# Settings

> Invite your team, set roles, choose which content products members can order, add writing guidelines, and create tokens for the API and MCP.

Source: https://docs.serpier.com/account-settings

Settings is where you set up your organization before you buy: who is on the team, which content products they can order, and the guidelines writers follow on every [order](https://docs.serpier.com/orders). It is also where you create tokens for the [REST API](https://docs.serpier.com/rest-api) and [Serpier MCP](https://docs.serpier.com/mcp). [Billing](https://docs.serpier.com/billing), [Notifications](https://docs.serpier.com/notifications), and [Connections](https://docs.serpier.com/connectors) are tabs on the same page and have their own pages.

Open **Settings** from the user menu at the bottom of the sidebar.

## Update your profile and sign-in

The **User** tab holds your personal settings. They apply to you, not to the rest of your organization.

- **Theme**: **Light**, **Dark**, or **System**. It applies to this device only.
- **Avatar** and **Name**: your profile photo and display name.
- **Change Password**: the password for email sign-in.
- **Providers**: sign in with Google or Microsoft as well.
- **Two-Factor**: adds a one-time password at sign-in.
- **Sessions**: where you are signed in. Revoke a session you do not recognise.
- **Delete Account**: removes your account permanently.

## Set up your organization

The **Organization** tab holds what applies to everyone in your organization. Only owners and admins can change it.

![The Organization tab with the organization name and contact email](https://docs.serpier.com/docs-assets/account-settings-organization.webp "Organization settings apply to everyone on your team.")

- **Name** and **Logo**: how your organization appears in Serpier.
- **Email**: your organization's **Contact email**.
- **Team Settings**: the name of the team you are working in.
- **Guidelines**: your requirements for the people who write your publications. They apply to every brief automatically; see [Add a brief](https://docs.serpier.com/orders#add-a-brief). Select **Add Guidelines** to write them.
- **Content types**: which content products members can order. Turn a type off and select **Save** to stop anyone ordering it from the [cart](https://docs.serpier.com/cart). At least one content type must stay available for each publication type.

## Invite people and set roles

1. On **Organization**, go to **Members** and select **Invite Member**.
2. Enter their email, choose a **Role**, and select **Send Invitation**.
3. They sign up or sign in, then select **Accept invitation** during onboarding to join your organization.

Open invitations wait under **Pending Invitations**. **Cancel Invitation** withdraws one.

To move someone between teams, find them under **Team Members** and select the edit icon. In **Member teams** you can add them to another team or remove one. A member has to stay on at least one team. Change their role from **Members**, not here.

## What each role can do

- **Owner**: everything an admin can do. Only an owner can make someone else an owner.
- **Admin**: changes organization and billing settings, invites people, cancels invitations, and changes other members' roles.
- **Member**: uses Serpier and can send invitations, but cannot change organization settings or anyone's role.

## Create a personal access token

A personal access token lets your own scripts and tools act as you: the [REST API](https://docs.serpier.com/rest-api) and MCP clients such as Cursor, VS Code, and Claude Code use one. Claude and ChatGPT do not need a token; they connect with OAuth on any plan (see [Serpier MCP](https://docs.serpier.com/mcp)).

1. On **User**, find **Personal access tokens** and select **Create personal access token**.
2. Give the token a name you will recognise, and create it.
3. Copy the token, which starts with `srpr_`. Serpier shows it only once.

![The Personal access tokens card on a plan without API access](https://docs.serpier.com/docs-assets/account-settings-api-keys.webp "Without the Enterprise API entitlement, the button reads Enterprise required.")

> Creating a token needs the Enterprise API entitlement on your organization. Without it, the card says **Enterprise API access required**. Publisher organizations can create tokens for the publisher deal endpoints without it; the card then says **Publisher API access enabled**.

A token works against the organization that is active when you use it. To stop a token working, delete it from the same card.

## Related

- [Billing](https://docs.serpier.com/billing.md)
- [Connections](https://docs.serpier.com/connectors.md)
- [Notifications](https://docs.serpier.com/notifications.md)
- [REST API](https://docs.serpier.com/rest-api.md)