Org Loom: Manage a Team workspace

Before you begin

Open Workspace from the canvas. A Team workspace has an owner, one or more admins, and members. Admins can manage most workspace settings; a few ownership and deletion actions are reserved for the owner.

Confirm the active workspace before changing anything. Membership, permissions, billing, AI-client access, and activity are all scoped to the workspace currently shown in the workspace switcher.

The four tabs

Account contains your Org Loom sign-in identity, account controls, and the option to join another workspace.
Workspace contains the name, members, permissions, feature settings, AI-client access, approvals, and invitations.
Billing contains the plan, Team seats, AI usage, credits, subscription controls, and payment portal.
Activity contains workspace events and Salesforce data-operation history for the active org.

Workspace settings showing a Team workspace, its members, roles, and admin controls

Manage members and roles

The Members section lists each person's role, email, join date, and any additional permissions granted to them.

Change a Member to Admin when they should manage members, settings, approvals, billing, and activity exports.
Change an Admin to Member to remove those admin controls. The last admin cannot be demoted or removed.
Choose Remove to end a person's workspace access. Their Org Loom account, personal workspace, and Salesforce connections are not deleted.

The owner can transfer ownership to another admin with Make owner. Promote the person to Admin first. Read the billing warning carefully: the previous owner's payment method remains on file until the new owner replaces it through the Stripe portal.

Manage member permissions

Select Permissions beside a member to grant or revoke sensitive capabilities such as running scripts, bulk editing, AI generation, AI access to canvas data, connecting orgs, uploading, recalling uploads, managing billing, and viewing activity history.

Manage billing and View activity history start off for every user. An admin can grant either permission without changing the person's workspace role.

Salesforce permissions still apply. An Org Loom feature permission does not grant object, field, or record access inside Salesforce.

Configure workspace features

Admins can change the settings available for the current plan:

Salesforce org approvals uses one policy to require approval for no orgs, production orgs only, or all orgs. Production only lets sandboxes, Developer Edition orgs, and scratch orgs connect without separate approval.
Require approval to join workspace places invite-code users in a pending queue until an admin approves them.

Only settings meaningful for the current plan are shown. Members can see the settings but cannot change them.

Manage AI client access

The AI client access (MCP) section is on the Workspace tab because each connection token is bound to both the user who generated it and the active workspace. It cannot act as another member, and it cannot be used to read or propose changes in another workspace.

Each member creates and revokes their own token. An admin can also revoke a member's token and grant or revoke that member's AI on canvas (MCP) permission. See Connect an AI client.

Invite teammates

Open Workspace → Invitations.
Choose Generate invite code.
Copy the invitation link, or share the code separately.
Revoke an outstanding invitation if it should no longer be used.

Invitations expire after one week and can be used once. Active members and outstanding invitations count toward the paid seat limit, so remove an unused invitation before creating another when the workspace is full.

If Require approval to join workspace is on, using the link or code creates a request under Invitations → Pending join requests. The person joins only after an admin approves it. See Join a workspace.

Manage Salesforce org access

The Salesforce org access section contains:

Pending requests from members blocked by an enabled org allowlist.
Approved access that an admin can review or revoke by member and org.

For a pending request, review the member and org, then choose Approve or Deny. Add a note when the reason will help the member. Salesforce org grants do not appear in the Members list, which is reserved for roles and Org Loom feature permissions. See Approve Salesforce org access.

Manage billing and seats

The Billing tab shows the current plan, price, AI usage, add-on credits, and subscription status for members with Manage billing. Other members see an explanation instead of billing details.

Use the Team seat stepper, then choose Update seats to confirm a change. Changing the number alone does not bill it.
A Team workspace must keep at least three seats and cannot reduce below its current member count.
Use Manage billing for payment methods, billing contact details, and invoices.
Use Buy AI credits for a one-time usage addition. See Buy and manage AI credits.
Use Cancel plan to schedule cancellation at the end of the current period. Resume plan reverses it before the period ends.

A failed payment appears in Billing. Update the payment method before the retry period ends. Org Loom keeps access during Stripe's normal payment-retry process.

Review and export activity

The tab is available to members with View activity history. Workspace admins receive this permission by default.

The Activity tab separates:

Workspace activity, such as membership, settings, permission, billing, and access decisions.
Salesforce data activity for the active org, such as uploads and other delivered record operations.

Filter by action or date, then choose Export CSV where available. Workspace activity and Salesforce data activity are exported separately because they are retained in different places. See Review activity history.

Leave or delete a workspace

A member can choose Leave this workspace. The last admin must promote another admin before leaving.
The owner can delete a non-personal workspace by typing its name and choosing Delete workspace.

Workspace deletion cannot be undone from Org Loom. It removes memberships, invitations, settings, grants, subscription, and workspace activity, and it ends access to the workspace's canvases through Org Loom. It does not delete Salesforce records or other Salesforce data.