Manage workspace members from the People tab

The People tab is the central place to manage the people in your workspace. Every workspace member appears here, whether they joined by invitation, through SSO, via SCIM, or as an external collaborator on a specific project. Workspace owners and admins can invite members, change roles, remove members, approve workspace and project access requests, and export the workspace member list as CSV. You can also track per-member credit usage and set individual credit limits that override workspace defaults. Open it from Settings → People.

​

People tab access and permissions

The tab is visible to every workspace role except external collaborators. What each role can do inside it varies.

• External collaborators do not see the People tab.
• Viewers can browse the member list, search, filter, sort, view any active member’s profile (if public), and export the CSV. They cannot take any management action.
• Editors can do and see everything viewers can, plus:
  • Invite and remove viewers and external collaborators
    On Enterprise plans, you can choose to only allow admins and owners to invite people by email. Go to Settings → Privacy & security → Restrict workspace invitations.
  • Approve project-level access requests.
• Admins can do and see everything except adding, removing, or promoting owners.
• Owners can do and see everything.
  Only owners can invite and remove owners, and promote existing members to owner.

​

The member list

The list shows every current member, including external collaborators, plus any pending invitations. Members who have been removed or who have left the workspace are not retained on this list. Available information:

• Name and email
• Role: Owner, admin, editor, viewer, or collaborator
• Joined date: When the member accepted an invitation or was provisioned
• Current month usage: Credits used this calendar month
• Total usage: Lifetime credit consumption on this workspace
• Credit limit: Monthly limit per member, either the workspace default as set in Workspace settings, or the individual override if set. Empty if neither is set.
  When a member hits their limit, they cannot consume more workspace credits until the 1st of the next month UTC.

Available actions:

• Search by name or email
• Filter by role
• Sort by name, role, joined date, current month usage, total usage, or credit limit
• Open a member’s row menu to:
  • View their profile in a new tab
  • Set an individual credit limit
  • Remove the member or revoke their pending invitation. On your own row, the remove option becomes Leave workspace.
• Change a member’s role by clicking the role dropdown next to their name in the role column
• Select multiple members for bulk actions (change role, set credit limit, remove members)
• Export the full workspace member list as a CSV

​

Invite members

You can invite members to join your workspace in two ways: invite by email or share an invite link (not available on Enterprise plans).

​

Invite by email

1. Go to Settings → People
2. Click Invite members
3. Enter one or more email addresses
4. Select a role:
   • Owner (can be selected only by an owner on Business and Enterprise plans)
   • Admin (available on paid plans)
   • Editor
   • Viewer (available on paid plans)
5. Click Invite

Pending invitations appear in the list with status Invited and can be revoked from the row menu.

​

Invite by link

1. Go to Settings → People
2. Click Invite link
3. Select the role:
   • Editor
   • Viewer (available on paid plans)
4. Click Create invite link
5. Copy and share the link

Invite links expire after 5 days and can be regenerated or deleted at any time.

• Only one active link per role is allowed at a time.
• Creating a new link replaces the previous one.

​

Automatic user provisioning

Beyond manual invites available in the People tab, Lovable can add members automatically. The provisioning options are configured in Settings → Identity. Provisioned members appear in the People tab, where roles and access can be managed.

• Just-in-time (JIT) provisioning: When a user signs in to Lovable through your configured SSO provider for the first time, they’re automatically added to your company workspace at the JIT default role you set (admin, editor, or viewer). See SSO for more information.
• Verified-email provisioning (domain-based provisioning): When a user signs up to Lovable with an email matching one of your verified domains, Lovable adds them at the configured default role (editor or viewer). This works for any sign-up on a verified domain, with or without SSO.
• SCIM provisioning (Enterprise): User and group lifecycle is managed centrally from your identity provider. When you assign a user to Lovable in the IdP, the user is created in the workspace at the configured role. Unassigning the user removes their membership, and changes to group membership or role mappings in the IdP are synced automatically. See SCIM for more information.

​

External collaborators

The collaborator role is designed for people outside your core team, such as freelancers, clients, contractors, or partners, who need access to specific projects but shouldn’t have broad workspace access. Collaborators can only:

• See basic workspace information
• See and open projects that have been shared with them (via the Shared with me tab on the Lovable dashboard)
• Open the Plans & credits and Cloud & AI balance tabs to see the current plan, credit balance, and usage, but every billing control is disabled for them. They cannot initiate or approve any charge against the workspace
• Leave the workspace

​

How are collaborators added?

The collaborator role is assigned when you invite a non-member to a specific project from that project’s Share dialog. They then appear in the People list as members of your workspace with the collaborator role. This lets you track their activity, set a per-member credit limit, and remove their access when needed. Collaborators cannot be invited from the People tab. On Business and Enterprise plans, Lovable warns you before inviting someone who isn’t a member of your workspace.

​

What project roles can collaborators have?

When sharing a project with someone, the Share dialog offers these project-level access options:

• Admin (available on paid plans): Full access to the project, including all project settings, integrations, and external connections.
• Editor (default on all plans): Can build, edit, and manage most project settings. Some advanced settings, like integrations and external connections, are reserved for admins.
• Viewer (available on paid plans): Read-only access to the project editor.

External collaborators receive whatever access level was selected in the Share dialog.

​

Why do collaborators consume my workspace credits?

In Lovable, credits belong to the workspace that owns the project. Every prompt draws from that workspace’s credit pool, regardless of who is prompting. External collaborators always consume your workspace’s credits, not their own.

​

Can I block or limit external collaborators?

Yes, if you are on Business and Enterprise workspaces and enable Enforce SSO, external collaborators are blocked by default until an owner or admin explicitly allows them. To block or limit external collaborator access:

1. Enable Enforce SSO in Settings → Identity.
2. Open Settings → Privacy & security and find the External collaborator access control.
   The External collaborator access setting only appears in the Privacy & security tab when Enforce SSO is enabled.
3. Choose one of the three modes:
   • Not allowed (default once Enforce SSO is enabled): Block external collaborators entirely. If members try to invite someone outside your organization to a project, they get an error informing them that this is not allowed.
   • Viewer only: External collaborators are capped at read-only access on every project they’re invited to.
   • Editor or below: External collaborators can have at most editor access.

​

What happens to existing external collaborators when external collaborator access settings change?

When you turn on Enforce SSO, Lovable shows a confirmation dialog with a Remove all external collaborators checkbox, on by default.

• If you leave it checked, existing external collaborators are removed at the same time SSO is enforced.
• If you uncheck it, existing external collaborators keep their access on every project they were already invited to, capped at editor level. The workspace’s External collaborator access setting is set to Editor or below as part of this flow.

If you later change External collaborator access to Not allowed, Lovable shows a similar confirmation dialog with a remove option. If you choose not to remove them, existing external collaborators remain in the People list but lose access. The next time they try to open the workspace or one of their projects, they see an External collaboration disabled error. If their email matches one of your verified domains, they’re redirected to sign in through SSO instead. A successful SSO sign-in provisions them as a full workspace member through just-in-time provisioning, and they’re no longer subject to the external-collaborator restriction.

​

Manage existing members

You can demote or promote existing members, remove members, or set individual credit limits from the People tab. This includes external collaborators as well.

​

Change a member’s role

To change a member’s role, click the role dropdown next to the member’s row, then choose a new role. Changes apply immediately.

• Only owners can promote existing members to owner.
• Existing members cannot be downgraded to collaborator. See External collaborators above.
• Existing collaborators can be promoted to a regular workspace role (viewer, editor, admin, or owner). After promotion, they become full workspace members with corresponding access. They’re no longer limited to specific projects.

​

Remove a member

To remove a member, click on the three dots menu from that member’s row, then click Remove. When you remove someone:

• Their workspace-level access is revoked immediately
• All of their project access within the workspace is revoked immediately
• For regular members (owner, admin, editor), any projects they owned are auto-transferred to the most senior remaining member of the workspace (owners first, then admins, then editors). External collaborators never own projects, so no transfer is needed.
  You cannot pick which member inherits their projects. If you want a specific person to take over their projects, transfer ownership manually from each project’s settings before removing them.
• This cannot be undone. Re-add the member by inviting them again.

​

Set a per-member credit limit

The workspace default applies to all members without overrides (set in Workspace settings). Individual credit limits apply only to members where an explicit credit limit has been set. To override the workspace default monthly credit limit for a member, click on the three dots menu from that member’s row, then click Set credit limit. When a member hits their limit, they cannot consume more workspace credits until the 1st of the next month UTC.

​

Bulk actions

Select multiple members using the row checkboxes, then use the bulk actions menu to:

• Change roles
• Set credit limits
• Remove members

​

Access requests

When someone tries to join the workspace or asks for access to a specific project, the request appears on the People tab.

​

Workspace access requests

People who discover the workspace through the Find workspaces flow can request to join it. The flow is driven by Workspace discovery, which is a Business and Enterprise feature. Business and Enterprise workspaces are discoverable by default. Owners and admins can turn this off in Privacy & security → Workspace discovery. The Find workspaces flow is available to accounts using non-public email domains (such as @yourcompany.com). Public domains like @gmail.com or @hotmail.com cannot discover or request access to workspaces this way. Each incoming request includes the role the requester is asking for (viewer, editor, or admin). Owners and admins can approve the request (granting the requested role, or a different role if you adjust it) or deny it.

​

Project access requests

When a workspace member or external user clicks through to a project they don’t have access to, they can request access at the role they need. Requests appear in the People tab for owners, admins, and editors. Workspace owners and admins can approve requests for any project in the workspace. Editors see all project access requests in the People tab, but can only approve requests for projects they have admin or owner access on. Approving a request grants the user the access level they requested on the specific project. Denying rejects the request without granting access. Approving a project access request does not change the user’s workspace-level role, only their access to that one project.

​

Related settings

​

FAQ