Manage workspace members from the People tab

The People tab is the central place to manage everyone in your workspace. Every member appears here, whether they joined by invitation, through SSO, via SCIM, or as an external collaborator on a 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 the workspace default. 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 all current members, including external collaborators, along with 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. When a workspace has more than one owner, the primary owner is marked Owner*.
• Joined date: When the member accepted an invitation or was provisioned
• Current month usage: Build credits used this calendar month
• Total usage: Lifetime build-credit consumption on this workspace
• Credit limit: Monthly build-credit 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 use more build credits until the 1st of the next month UTC.

Available actions:

• Search by name or email
• Filter by role, or by SCIM-managed status for Enterprise workspaces with SCIM configured. This lets you show SCIM-provisioned seats or non-SCIM seats. The selection is reflected in the URL, for example ?scim=managed or ?scim=unmanaged, so deep links and browser navigation work.
• 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)
• Import limits on Enterprise plans: set per-member credit limits in bulk from a CSV
• Export the full workspace member list as a CSV

​

User insights

Click any member row to open a User insights profile. Workspace owners and admins can use it to review what a member does in the workspace without leaving the People tab, for example to audit seat usage, set sensible credit limits, or review project access before offboarding. The profile shows:

• Identity: the member’s name, email, workspace role, and a SCIM badge if the seat is provisioned through your identity provider
• Credit usage: credits used in the last 7 days and the last 30 days
• Created: projects the member created in the workspace, with visibility and per-project credit usage over the last 30 days
• Collaborated on: projects the member has direct access to, with their access level, per-project credit usage, and a Pending badge for project invitations they have not yet accepted

Project lists are sorted by latest edit by default, and you can switch to sorting by highest usage. Clicking a project opens it in a new tab. On Enterprise workspaces with audit logs, the profile also includes an Activity tab showing the member’s recent workspace actions. The profile is read-only. To change a role, set a credit limit, or remove the member, use the member list actions described above.

​

Invite members

You can invite members in two ways: by email or with an invite link (not available on Enterprise plans). Invites can also be blocked with an “Invite was blocked due to suspicious activity” message by automated fraud checks. There is no self-serve way to lift this block. If you believe it is a mistake, contact Lovable Support.

​

Invite by email

1. Go to Settings → People
2. Click Invite members
3. Enter one or more email addresses
4. Select a role:
   • Owner (only available to existing owners 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. Email invites are valid for 30 days, and the invitation email states the expiry date. After 30 days, the invite disappears from the People list, the link in the invitation email stops working, and the invitation no longer grants access through any other path, such as domain auto-join or SSO sign-in. This also applies to invitations that were already pending when the 30-day limit was introduced. To bring someone in after their invite expires, invite them again. A new invitation starts a fresh 30-day window.

​

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 can exist at a time.
• Creating a new link replaces the previous one.

​

Automatic user provisioning

Beyond manual invites available in the People tab, Lovable can automatically add members. The provisioning options are configured in Identity (Settings → Access → Identity); see Manage workspace identity and user provisioning for the full setup. Provisioned members appear in the People tab, where roles and access can be managed.

• SSO sign-in (just-in-time, or 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). On Enterprise plans, owners and admins can toggle this from the SSO sign-in row once an SSO provider is configured; on Business plans, it’s enabled automatically with a configured SSO provider and shown as a read-only status. See SSO for more information.
• Verified email sign-up (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.
• Add existing users: A one-time action in the Identity tab that adds people who already have Lovable accounts with verified-domain emails to your workspace, so you don’t have to wait for them to sign in or sign up again.
• 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. SCIM is configured separately from the User provisioning section. See SCIM for more information.

​

External collaborators

The collaborator role is 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 access projects that have been shared with them (via the Shared with me tab on the Lovable dashboard), according to the assigned project access level
• Open the Plans & credit usage tab 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 collaborators are added

The collaborator role is assigned when you invite a non-member to a project from that project’s Share dialog. After that, they 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.

​

Project access levels for collaborators

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.

​

How collaborators use 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.

​

Block or limit external collaborators

On Business and Enterprise workspaces, owners and admins can control whether people outside the workspace can be added as project collaborators, and the highest project role they can have. This setting is available whether or not you enforce SSO. When Enforce SSO is on, external collaborators are blocked by default until an owner or admin explicitly allows them. To block or limit external collaborator access:

1. Open Settings → Privacy & security and find the External project collaborators control.
2. Choose the highest project role someone outside the workspace can have:
   • None allowed: 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.
   • Allow viewers: external collaborators are capped at read-only access on every project they’re invited to.
   • Allow editors and viewers: external collaborators can have at most editor access.
   • Allow all: external collaborators can be given any project role, including admin.

​

How access setting changes affect existing collaborators

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 project collaborators setting is set to Allow editors and viewers as part of this flow.

If you later change External project collaborators to None 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 take effect immediately. When you make someone an admin or owner, Lovable shows what the role includes and asks you to confirm first, and the workspace’s admins and owners receive an email about the change.

• Only owners can promote existing members to owner.
• The primary owner cannot be demoted. To change who the primary owner is, transfer primary ownership first.
• 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.

​

The primary owner

A workspace can have several owners, but one of them is the primary owner. Lovable uses the primary owner for billing and for domain claims. When a workspace has more than one owner, the primary owner is marked Owner* in the member list, and the marker’s tooltip reads “This is the primary owner, used for billing and domain claims.” A workspace with a single owner shows no marker. You cannot demote the primary owner, on their own or in a bulk role change. You can still demote other owners. To change who the primary owner is, transfer primary ownership.

​

Transfer primary ownership

Only the current primary owner can transfer primary ownership. Every plan includes this option.

1. Go to Settings → Workspace.
2. Under Workspace access, find Transfer primary ownership and click Transfer.
3. Under New primary owner, select an active workspace member, or enter the email address of another Lovable account. The address must be a verified email on exactly one Lovable account.
4. If the person is not in the workspace, or is a viewer or an external collaborator, Lovable warns that the transfer gives them full owner access. Lovable shows no such warning for owners, admins, or editors.
5. Click Transfer.

After the transfer:

• The person becomes the primary owner. If they were not already an owner, Lovable promotes them to owner. Someone outside the workspace joins it as an owner immediately, with no invitation to accept. On Free and Pro plans, a person who was not already an owner, admin, or editor counts toward the 200-member limit, so the transfer fails when the workspace has reached that limit.
• You remain an owner of the workspace. Only the new primary owner can transfer primary ownership again.
• The workspace’s owners and admins, including you and the new primary owner, receive an email about the change. On Enterprise plans, the transfer is recorded in the audit logs.

​

Remove a member

To remove a member, click the three dots menu from that member’s row, then click Remove member. You cannot remove the workspace’s only owner. When you remove someone:

• Their workspace-level access is revoked immediately
• All of their project access within the workspace is revoked immediately
• They receive an email letting them know they were removed from the workspace
• For regular members (owner, admin, editor), the projects and folders they owned are transferred to another member. You choose the recipient or keep the default. See Choose who inherits their projects. External collaborators never own projects, so no transfer is needed.
• This cannot be undone. To restore access, invite them again.

​

Choose who inherits their projects

When you remove an active member who owns projects, the Remove workspace member? dialog asks who should receive them before Lovable completes the removal.

• Transfer their projects to (the label shows how many projects will transfer): select any active owner, admin, or editor in the workspace, including yourself. The default, Member with the highest role (automatic), gives the projects to the remaining member with the highest role (owners first, then admins, then editors). If two members share the highest role, the one who joined earliest receives them. Below the list, Lovable notes that their workspace folders move with the projects.
• If any of their projects are published to the web, Lovable warns you. To take the transferred projects offline as part of the removal, select Unpublish the transferred projects. Projects published to your workspace only remain online.

Click Transfer and remove to confirm. If the member owns only Restricted projects, Lovable shows no recipient list, and the button reads Remove member. Four exceptions apply:

• Projects whose access is set to Restricted are not transferred and keep the removed member as their owner. The dialog says how many are left out and does not count them in the transfer. A workspace owner has to transfer them manually from the dashboard or from project settings, because workspace owners can open every project, including Restricted ones. A published Restricted project stays online.
• Their personal folders never go to the recipient you selected. They always go to a workspace owner. When the workspace has several owners, the one who joined earliest receives them.
• Connections the member created remain in the workspace with their existing access settings. Workspace admins and owners can delete them.
• Lovable transfers projects automatically, with no choice of recipient, when you remove several members at once, when a member leaves the workspace, and when SCIM deprovisions a member.

​

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. To set limits for many members at once on Enterprise plans, import them from a CSV instead. Member credit limits count build credits only. Run credits (consumed when Lovable hosts your app and runs its built-in backend (Cloud), including AI features in deployed apps) belong to the project, not to the member who built it, so they never count toward a member’s limit. See Credits and usage. When a member hits their limit, they cannot use more build 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

​

Import credit limits from a CSV

On Enterprise workspaces, workspace owners and admins can set a different credit limit for each member in one upload instead of editing members one at a time. On the All tab, select Import limits, then upload a CSV with an email and a monthly_credit_limit column, or start from the downloadable template. Each limit is the member’s final monthly cap, not an amount added to their current limit. Decimals and 0 are valid, and a limit of 0 blocks new credit usage for that member. A file can hold up to 1,000 rows and must match active workspace members by email. Rows for pending invitees are rejected. Lovable validates the file and shows a preview with a per-row status before anything is applied. Every row must be valid before you can select Apply limits. Fix or remove the rows marked Error and upload the file again. The import overwrites each listed member’s current limit with the value in their row. To take a member off their individual limit so that the workspace default applies again, enter default in the limit column instead of a number. An empty limit cell is a validation error, not a cleared limit, so a blank cell can’t remove someone’s limit by accident. To change or clear one member’s limit without a file, use Set credit limit from their row menu. 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, but can only approve requests for projects where they have admin or owner access. 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