# Organizations and members What an organization is, how people sign in and join, and where organization and personal settings live. Canonical page: https://app.auto-lab.ai/docs/organization Your organization is the level above your goals. It holds the goals, the people who work on them and the settings they share. This page covers signing in, inviting people and finding your way around both kinds of settings. ## What an organization holds - **Goals.** Every goal belongs to one organization. - **People.** Each member has an organization role, and a role on each goal they work on. See [Roles and access](/docs/organization/access). - **Shared settings.** The organization's name and sign-in rules, its GitHub connection, its API keys and, if your organization has them, single sign-on and branding. The first time you sign in, Auto Lab creates an organization of your own, named after your email address. If it has no goals yet, Auto Lab creates a first one and opens its setup. You can rename the organization in **Organization settings › Settings**. An organization becomes a team when more people join it. Only owners and admins of an organization can create goals in it. You can belong to several organizations at once. ## Sign in ### Enter your email Open Auto Lab, type your email address and choose **Continue**. There is no separate sign-up: a new address gets an Auto Lab account automatically. ### Enter the code Auto Lab emails you an 8-digit code. Type or paste it on the **Check your email** screen. If it does not arrive, choose **Resend** once the timer runs out. Other ways in: - **Use a password instead** on the code screen. **Forgot your password?** sends a reset link. - **Continue with Google**, when Google sign-in is switched on. - **Use single sign-on (SSO)**, if your organization signs in through its identity provider. If your email domain requires it, **Continue** takes you straight there. Auto Lab can run invite-only. Then an address without an invitation sees **Auto Lab is invite-only** and a short form: email, company and what you hope to automate. Choose **Request access** and the Auto Lab team replies by email when there is a spot. ## Accept an invitation Invitations come in two kinds. | Invitation | What you see | What happens | |---|---|---| | To Auto Lab itself | An email titled "You're invited to Auto Lab", or "Set up Acme on Auto Lab" for a team called Acme | **Accept invitation** opens sign-in with your address filled in. Sign in with the emailed code. | | To a colleague's organization | An email with a link to the invitation | Open the link and choose **Accept** or **Decline**. Signing in with the invited address also adds you. | A team invitation carries a number of seats. The first person to accept sets the team up: their organization takes the team's name and seats, and they can invite colleagues from there. Invitations to Auto Lab expire after 14 days. If you are signed in with a different address from the one invited, the page says whose invitation it is. Sign out and sign back in with the invited address. If a link has expired or was withdrawn, ask the person who invited you for a new one. ## Invite teammates Owners and admins can invite people. ### Open Members Open **Organization settings › Members** and choose **Invite**. ### Pick people and a role Type an email address to invite someone new, or pick people who are already in the organization. Everyone you select gets the same role. ### Send Each person gets an email with a link. Open invitations wait under **Invited**, with the date each one expires. Use the menu on a row to **Resend invite**, **Copy invite link** or **Cancel invite**. If Auto Lab set your team up with a number of seats, each person uses one. When they are all taken, the invite is refused with "Your team has used all its seats. Ask Auto Lab for more." Write to hello@auto-lab.ai for more. To bring someone into one goal only, grant them access from that goal instead. See [Give someone access to a goal](/docs/organization/access#give-someone-access-to-a-goal). ## Switch organizations - **In a goal:** open the goal switcher at the top of the rail and choose **Switch goal**. With more than one organization, the list groups goals under each organization's name. Picking a goal in another organization moves you there. - **On the Goals home:** the menu at the top left scopes the page to **All accounts** or to one organization. - **In Personal settings › Profile:** **Organizations** lists each one with your role. **Manage** opens its settings. ## Organization settings Open the goal switcher, choose **Switch goal**, then **Organization settings**. Owners and admins see every section; members see only the ones their role can use. | Section | What it holds | |---|---| | **Settings** | The organization's name, its two-factor and sign-in rules, and deleting the organization (owner only). | | **Branding** | Your logo, icon, favicon and product name for everyone in the organization. An enterprise feature. | | **Git** | The GitHub connection your goals use to create or import repositories. | | **API keys** | Service account tokens for CI and automations, apps that sign people in with Auto Lab, and key rules. | | **Members** | Everyone in the organization, their roles, and open invitations. | | **Groups** | Sets of people you grant access to together. | | **Projects** | Every goal's access in one list. Pick a goal to see who is in it. | | **Roles** | The built-in roles and, if your organization has them, custom roles. | | **Identity** | Single sign-on and SCIM provisioning from your identity provider. An enterprise feature. | | **Audit log** | Who did what, where and when. An enterprise feature. | | **Help** | A short explanation of how access works. | | **Usage** | What each goal and session cost. See [Usage and limits](/docs/organization/usage). | Enterprise features show an explanation and **Request a demo** until Auto Lab switches them on for your organization. ## Personal settings Personal settings belong to you, not to an organization. Open the goal switcher and choose **Settings**, or press ⌘, on a Mac or Ctrl+, elsewhere. | Section | What it holds | |---|---| | **Profile** | Your picture, name and email, and the organizations you belong to. | | **Security** | Two-factor authentication with an authenticator app, and signing out your other devices. | | **Chat identities** | The Slack, Teams and iMessage identities you linked, so a goal knows who is writing. See [Channels](/docs/connect/channels). | | **Connectors** | Your own connections to a goal's apps. See [Connectors](/docs/connect/connectors). | | **MCP** | Connect an AI client to your goals. See [MCP](/docs/developers/mcp). | | **Secrets** | Your own values for a goal's secrets, which override the shared ones for you. See [Secrets](/docs/connect/secrets). | | **Appearance** | Theme, wallpaper and how much detail a conversation shows. | | **Notifications** | Browser notifications for finished work, errors, questions and permission requests. | | **Language & shortcuts** | The app's language and keyboard shortcuts. | | **Personal access keys** | Keys that act as you, for the CLI, a script or a CI job. See [Access keys](/docs/organization/access#access-keys). | ## When access ends An owner or admin can remove a member from **Organization settings › Members**. The person loses that organization's goals, and their personal access keys for it stop working. Their other organizations are not affected. The Auto Lab team can also end access, for example when a pilot finishes. The person then sees "Your access to Auto Lab has ended", with **Talk to us** and **Sign out**. When a whole organization's access ends, its agents and API keys stop working too. Nothing is deleted: goals and data stay as they were, and access can be restored.