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

# User types & permissions

> A breakdown of the three user roles in Parabola — what each can do, how admin permission scopes work, and how to manage user access at the org level.

Every time someone joins your Parabola team, you'll need to decide what level of access to give them. The answer shapes what they can build, what they can see, and what they can change — including things like billing and team membership.

***

## Adding users to your organization

Adding a new user to Parabola is entirely self-serve — no need to go through the Parabola team. Any admin can do it directly from the [Team page](https://parabola.io/app/team).

<Steps>
  <Step>
    Navigate to the [**Team page**](https://parabola.io/app/team) and click **+ Add teammate**.
  </Step>

  <Step>
    Enter their name and email address.
  </Step>

  <Step>
    Assign a role: **Admin**, **Editor**, or **Viewer** (described below).
  </Step>

  <Step>
    Click **Add teammate**. They'll receive an email invitation with instructions to set up their account.
  </Step>
</Steps>

<Tip>
  When adding a new team member, assign the minimum role they need to do their job. You can always upgrade their access later.
</Tip>

***

## The three user types

| Role       | What they can do                                                                                                         |
| ---------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Admin**  | Manage subscription and billing, add and remove team members, monitor usage analytics, and access all admin capabilities |
| **Editor** | Create and edit flows — no billing or user management access                                                             |
| **Viewer** | Read-only access to flows they've been explicitly given access to                                                        |

***

## Admin permission scopes

On **Advanced and Enterprise plans**, admin access is broken into four distinct scopes. On all other plans, admins have User and Billing permissions only.

| Scope                   | What it includes                                                                                                       |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **User permissions**    | Add and remove team members; change permission levels                                                                  |
| **Billing permissions** | Change subscription plan; update payment method                                                                        |
| **Content permissions** | Access, edit, and move all flows in the organization — including flows not in shared team folders; delete team folders |
| **Org Admin**           | All of the above, plus the ability to manage other admins                                                              |

<Note>
  If you need to remove your own Org Admin status, reach out to [Parabola support](mailto:help@parabola.io).
</Note>

***

## Managing billing

If you have billing permissions, you can update your payment method from the [Billing page](https://parabola.io/app/billing).

For plan changes or questions about your subscription, contact your Parabola account manager or email [help@parabola.io](mailto:help@parabola.io).

***

## SSO and centralized login

If your organization uses a centralized identity provider (like Okta, Google Workspace, OneLogin, or Azure AD), you can connect it to Parabola through Single Sign-On (SSO).

Parabola uses **WorkOS** to support SSO. Setup requires a brief coordination call with the Parabola team to exchange configuration details with your IT team — the process typically takes about 15 minutes.

Once SSO is configured:

* Users sign into Parabola using the **"Sign in with SSO"** option
* All ongoing user management (inviting users, removing users, updating permission levels) continues to happen from the **Team page in Parabola**
* Changes made in your identity provider directory are **not** automatically synced to Parabola — you'll need to reflect those changes manually

<Tip>
  For full SSO setup instructions, see the [SSO configuration guide](/product/security/sso-configuration).
</Tip>

***

## What admins can see that others can't

Beyond user and billing management, admins have a few capabilities editors and viewers don't:

* **Usage analytics** — Admins can access credit consumption data broken down by user and by flow (covered in Lesson 4)
* **Full flow access** — Content admins have edit access to all flows in the organization, even ones they haven't been directly shared on

***

## What's next

Now that you understand the different user roles and how admin access works, the next lesson covers credits — what they are, how they're calculated, and how your team consumes them.

***

<Card icon="sparkles" title="Building challenge">
  Navigate to your [Team page](https://parabola.io/app/team) and review the current roles assigned to your team members.

  * Is everyone assigned the right role?
  * Are there any users who should be upgraded to Admin — or downgraded to Viewer?
  * Are there any admins with broader scope than they need?
</Card>