Team Management

Chipp supports multi-user organizations so you can collaborate with your team on building, managing, and deploying AI agents. This guide covers inviting members, assigning roles, and organizing work with workspaces.

Organization Structure

Every Chipp account belongs to an organization. An organization contains:

• Members: People who can access the organization
• Workspaces: Logical groupings of apps (like folders)
• Apps: The AI agents your team builds

Members are invited at the organization level, then assigned to one or more workspaces with specific roles.

Roles

There are four roles in Chipp, each with different permissions:

Role	What They Can Do
Owner	Full control. Manage billing, invite/remove members, delete the org. Cannot be removed by others.
Admin	Invite members, manage workspaces, configure apps. Cannot manage billing or delete the org.
Member	Build and configure apps within assigned workspaces. Cannot invite members or manage org settings.
Viewer	Read-only access to apps and chat history. Cannot modify anything.

Inviting Team Members

For a quick invite without picking a role or workspaces, Settings > Team also has an Invite button. It asks only for an email address and adds the person with the Member org role.

Workspace-Level Invites

You can also invite members directly from a workspace’s member list. Workspace-level invites automatically assign the “Member” org role and add the person to that specific workspace.

Managing Members

Viewing the Team

Go to Settings > Team to see all organization members. The page shows:

• Member name and email
• Role
• Status (Active or Deactivated)
• A count of total members

Use the filter box to search by name or email. Settings > Access Control > Members shows the same people with their org role, workspace assignments, and status.

Changing Roles

Owners can change any member’s role. Admins can change roles for Members and Viewers. To change a role:

1. Find the member in the team list
2. Click the role dropdown next to their name
3. Select the new role

Deactivating Members

Rather than deleting members outright, you can offboard them. Offboarded members are deactivated: they cannot log in, but their activity history is preserved. To offboard:

1. Go to Settings > Access Control > Members
2. Find the member
3. Click the offboard icon and confirm

A deactivated member can be restored with Reactivate on the same page. (Settings > Team also has a remove button, which removes the person from the organization.)

If the deactivated member was the sole Owner of any workspace, another member is automatically promoted to Owner of that workspace to prevent orphaned workspaces.

Workspaces

Workspaces let you organize apps into logical groups. Common patterns:

Pattern	Example Workspaces
By client	”Acme Corp”, “Beta Inc”
By function	”Customer Support”, “Sales”, “Internal Tools”
By environment	”Production”, “Staging”, “Experiments”

Creating a Workspace

1. Click the workspace switcher in the left sidebar
2. Click New Workspace
3. Enter a workspace name

Workspace Members

Each workspace has its own member list with workspace-specific roles:

Workspace Role	Permissions
OWNER	Full control over the workspace and its apps
EDITOR	Create, edit, and publish apps
VIEWER	Read-only access to apps and chat history

To manage workspace members:

1. Open the workspace
2. Go to Settings > Members (under Workspace)
3. Add or remove members, or change their workspace role

Workspace Spending Limits

Owners can set a monthly spending limit on a workspace to control LLM costs:

1. Go to Settings > Settings (under Workspace)
2. In Usage & Budget, set the Monthly spending limit in dollars
3. When the limit is reached, apps in that workspace stop responding until the next billing period

You can also set per-member spending limits in the Member Budgets section for finer control.

Role Templates and Permission Overrides

Workspace roles give broad access. Two tools let you fine-tune it: role templates (which can raise or lower access) and member overrides (which can only lower it). They are not the same thing.

How Chipp decides what a member can do

For each permission area (such as Publishing or Billing), Chipp checks these steps in order for a workspace member:

1. Workspace Owners are never restricted. A workspace Owner always has full access. Role templates and overrides do not apply to them. Organization Owners and Admins who are not members of a workspace also get Owner-level access there.
2. Start from the base. If the member has a role template and the template sets that area, the template’s value is the base. Otherwise the base is the workspace role’s default (Editor or Viewer).
3. Apply the member override, if there is one. An override can only lower the base. If an override asks for more than the base allows, Chipp ignores the extra and uses the base.

Role templates are checked live. If you edit a template, every member who has it gets the new access on their next action. You do not need to reapply it.

Grant access with a role template

To give someone access that their role does not include, put it in a role template and assign the template to them:

1. Go to Settings > Access Control > Role Templates and create or edit a template. Set each permission area to None, Read, or Write.
2. Open the workspace, go to Settings > Members (under Workspace), and assign the template to the member from their role dropdown. You can also pick a template when you invite someone.

Assigning a template from the dashboard makes the member an Editor in that workspace, with the template deciding each area it sets. Areas the template does not set keep the Editor default. Changing the member’s workspace role later removes the template and any overrides.

Example: let an Editor manage the workspace HQ. Editors can view the HQ but not change it by default. Create a template that sets Workspace HQ to Write, then assign it to that Editor. Their other areas stay as the Editor default.

Limit access with a member override

A member override takes access away from one member without changing their role or template. Overrides can lower a permission area from Write to Read or None, or from Read to None. They can never raise it.

Overrides are set through the API, not the dashboard. Send PATCH /api/organization/rbac/members/:userId/workspaces/:workspaceId/permissions with a permissions object, for example { "publishing": "none" }. The call replaces the member’s earlier overrides. Anything that would raise access above the member’s role default is dropped when it is saved. The person making the call needs Write access to member management in that workspace.

Example: stop one Editor from publishing. Set { "publishing": "none" } as an override for that member. They keep every other Editor permission and lose Publishing. Other Editors are not affected.

If you want a reusable restriction for several people, create a role template instead and assign it to each of them.

Plan Requirements

Inviting members, role-based access control, and role templates are available on every plan. Only organization owners and admins can manage members and role templates.

Some counts still depend on your plan:

Limit	Free	Builder and above
Workspaces	1	Unlimited
Members per workspace	1	Unlimited

Troubleshooting

Invite Not Received

1. Check the spam/junk folder
2. Verify the email address was entered correctly
3. Revoke the pending invite under Pending Invites in Settings > Team, then send a new one
4. Invites expire after 7 days — send a new one if expired

Member Can’t See Apps

Members only see apps in workspaces they’ve been assigned to. Check that the member has been added to the correct workspace.

Can’t Change a Member’s Role

Only Owners can change roles to Admin. Admins can only change roles for Members and Viewers. You cannot change the role of someone with a higher role than your own.