RudderStack Docs – Workspaces and Collaboration

Lookout: Roles and Permissions in Rudder Lookout

Mon, 01 Jan 0001 00:00:00 +0000

Access within a Lookout workspace follows clear roles. Every member can chat, build dashboards, and read and write knowledge, while configuration and connected accounts are reserved for admins and the owner. Unregistered users can be given read-only guest access.

Workspace roles

Membership comes with one of three primary roles:

These roles and boundaries are enforced by Lookout, not just hidden in the interface.

Role	What they can do	Notes
Member	Use the chat agent, build and view dashboards, read and write Context Hub docs and notes, and work with Measurement Plans	The everyday working role — they get the full conversational product but can’t change team configuration or connected accounts
Admin	Everything a member can do, plus edit settings, connect warehouses and data sources, manage the RudderStack and Slack connections, create invites, and add, remove, promote, or demote members	Admins are peers — any admin can change another admin’s role. The owner is the only exception — they can’t be demoted or removed
Owner	Everything an admin can do, plus rename and delete the workspace	Every workspace has exactly one owner — the person who created it

Guest access (read-only)

Beyond the three member roles, Lookout also supports guest access for people who are not registered workspace members. Guests can read and ask, but never edit or change — they can’t edit dashboards, write to connected systems, or act on the team’s behalf.

Guest access is available in two contexts:

1. Slack

A Slack user who hasn’t yet linked a Lookout account can ask read-only questions in bound channels and DMs. Guest access is enabled by default. However, an admin can disable it via the Allow guest access in Slack toggle under Settings > Slack.

Once a user links their account (with /lookout connect), they act as their full workspace identity. See the Slack integration guide for more information.

2. Public links

Anyone with an access to a public dashboard link can view it read-only, without sign-in. Public sharing is controlled by an admin.

Membership and trust

A member and an admin share the same connected systems for the team. For example, the team’s RudderStack connection is configured once for the whole workspace, so anyone who can drive the chat agent works through the same connection.

Treat workspace membership itself as the meaningful access decision — roles separate configuration duties from everyday use. See Security and Data Handling for more information.

Add and manage members

Owners and admins can manage members from Settings > Members, and add new people with invite links.

Lookout: Invite Teammates in Rudder Lookout

Mon, 01 Jan 0001 00:00:00 +0000

This guide explains how to invite members to a Lookout workspace.

Create an invite link

Only owners and admins can create invite links.

Go to Settings > Members > Invite Links.
Select Create Invite to generate a link.
Copy the link and share it with the people you want to add.

How invite links work

Each invite link:

Expires after 7 days. Once expired, it stops working and anyone using it sees “This invite has expired.” Generate a new link to continue inviting.
Can be revoked at any time. Select the trash icon next to a link to disable it immediately, even before it expires.

Note that:

Anyone who accepts the link joins the workspace as a Member.
There is no per-link cap on the number of people who can join — a link works for unlimited joins until it expires or is revoked.

Because a single link allows unlimited joins until it expires or is revoked, generate links only for people you intend to add, and revoke any link you no longer need.

Accept an invite

When a recipient opens the link and accepts, they are added as a workspace member. Because sign-in is workspace-agnostic, nothing else is needed — once accepted, the new member can navigate to the workspace and start working.

Owners and admins can manage a member’s role by going to Settings > Members and selecting the member. See Roles and Permissions for more information.

Lookout: AI Credits in Rudder Lookout

Mon, 01 Jan 0001 00:00:00 +0000

This guide explains how to track AI usage in a Lookout workspace.

Overview

AI credits measure how much AI usage your workspace consumes. You can review your usage from Settings > AI Credits, which shows your credit usage for the selected period, a breakdown by action, and a detailed usage log.

What you can see

Credit usage for the selected period: Running totals for your workspace, for the month you select and its calendar year
Credit usage by action: Actions that consume credits, and their share of the total
Usage details: A log of individual actions, including the action, who triggered it, the date, and the credits it used

Credits measure AI usage, not money. How credits map to billing is handled separately, at the RudderStack account level. Use the AI Credits page only to understand and monitor your team’s usage.

What consumes credits

Different actions like opening a chat, creating a dashboard, indexing a source, raising a pull request, etc. consume varying credits. The Credit usage by action breakdown on the AI Credits page shows where your workspace’s credits are going.

Detailed credit pricing that explains how many credits each action costs is being finalized and will be documented soon.

For current pricing and how credits map to your plan, contact Customer Success.