> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alkera.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams & members

> Organizations, teams, roles, invitations, and sign-in settings.

export const Enterprise = ({title = "Enterprise", children}) => <Card title={title} icon="building-lock" href="mailto:sales@alkera.ai" cta="Contact sales" arrow horizontal>
    {children}
  </Card>;

An **organization** is your company's account in Alkera. It owns your members, teams, [connections](/foundations/plugins-and-connections), [knowledge](/foundations/knowledge-base), [machines](/workspaces/machines), and [billing](/organization/billing).

Inside it, **teams** group people. Teams nest as deep as you need, so a team can hold sub-teams. A person can be on as many teams as you like.

When you sign up without an invitation, Alkera creates a new organization and makes you its first admin.

## Teams

Open **Teams** from the **Organization** section of the sidebar. The team tree shows every team and its sub-teams. Choose a team to see its roster, with members who joined directly and members who belong through a sub-team.

Teams decide:

* Who can use a team's [connections](/foundations/plugins-and-connections#personal-and-team-connections).
* Who you can [share](/workspaces/overview#sharing) workspaces and files with in one step.
* How credit is [allocated](/organization/billing#allocations) across the organization.

## Roles

There are two roles: **Member** and **Admin**. A role is held per team, so the same person can be an admin of one team and a member of another.

| | Member | Admin |
| - | - | - |
| Use the team's connections, chats, and knowledge | Yes | Yes |
| Invite people and revoke invitations | No | Yes |
| Manage members and sub-teams | No | Yes |

Admin rights descend. An admin of a team is an admin of every team beneath it. An admin of the top team is an **Org admin**, and is an admin everywhere.

Org admins also manage organization settings, [billing](/organization/billing), [Slack](/workspaces/slack), and sign-in. Org admins and team admins can manage [machines](/workspaces/machines).

## Invitations

An admin invites someone by email and picks the team and role they join with.

<Steps>
  <Step title="Send">
    Alkera emails a sign-up link. The invitation is good for seven days.
  </Step>

  <Step title="Accept">
    The recipient signs up through the link, or clicks **Accept invitation** if they already have an account. They join the team and every team above it.
  </Step>
</Steps>

If you invite someone who already belongs to your organization, they are added right away with no email. An admin can revoke a pending invitation before it is used.

<Tip>
  Invite colleagues rather than having them sign up on their own. Signing up without an invitation creates a separate organization.
</Tip>

## Multiple organizations

You can belong to more than one organization, such as your company's and a client's. Each organization keeps its own workspaces, files, connections, knowledge, and billing.

Switch organizations from the account menu, under your profile icon at the bottom left of the sidebar:

* **Switch organization** lists the organizations you belong to, with a check next to the one you are in. Choose another to switch to it.
* **Create organization**, at the end of that list, starts a new organization with you as its admin.
* **Pending** lists organizations that added you, for example through their directory, but that you have not joined yet. Click **Join** to join one. It then appears under **Switch organization**.

When you belong to more than one organization, the account menu shows which one you are in.

## Organization settings

Org admins open **Settings** from the account menu at the bottom of the sidebar. The **General** tab has:

* **Organization name** and **Members**.
* **Sign-in methods**: allow or turn off sign-in with Google and GitHub.
* **Slack**: connect the [Slack app](/workspaces/slack).
* **Knowledge sync**: allow sharing [knowledge](/foundations/knowledge-base#knowledge-sync) across the organization.

## Single sign-on

Organizations on the Enterprise plan can connect an identity provider in **Settings** under **Single sign-on**.

* **SSO** over OIDC or SAML, for your organization's email domains. Turn on **Require SSO** to hide password sign-in.
* **Group → role mapping** assigns roles from your identity provider's groups.
* **Automated provisioning (SCIM 2.0)** adds and removes members from your directory. Generate a token and give it to your identity provider. The token is shown once.
* **Audit log** records activity in your organization.

<Enterprise title="SSO, SCIM, and audit log">
  Single sign-on, directory sync, and the audit log are available on the Enterprise plan.
</Enterprise>

## Related

<Columns cols={2}>
  <Card title="Billing & usage" icon="credit-card" href="/organization/billing">
    Plans, credits, and team allocations.
  </Card>

  <Card title="Plugins & Connections" icon="plug" href="/foundations/plugins-and-connections">
    Personal and team connections.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.