> For the complete documentation index, see [llms.txt](https://docs.quper.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quper.co/get-started-with-quper/onboarding.md).

# Onboarding Your Team

Quper is built for collaboration across FinOps, DataOps, platform engineering, and finance teams. This guide covers how to invite users, assign roles, and set up access controls so every team member sees exactly what they need.

## Inviting users

{% stepper %}
{% step %}
**Go to Settings → Users**

From the left sidebar, navigate to **Settings → Users & Access**. Click **Invite User**.
{% endstep %}

{% step %}
**Enter the user's email**

Type the email address of the person you want to invite. Quper will send them an invitation link that expires after 48 hours.
{% endstep %}

{% step %}
**Assign a role**

Select a role for the new user. Quper ships with three default roles:

| Role       | What they can do                                                                  |
| ---------- | --------------------------------------------------------------------------------- |
| **Admin**  | Full access to all settings, integrations, billing data, and user management      |
| **Editor** | Can view all cost data, create dashboards, set budgets, and apply recommendations |
| **Viewer** | Read-only access to cost data, dashboards, and reports                            |

You can also create custom roles with granular permissions. See [Role-Based Access Control](/settings/rbac.md) for details.
{% endstep %}

{% step %}
**Set data access scope (optional)**

If you want to restrict what cost data this user can see, assign them to a **Team** in Settings → Teams. Users in a team only see cost data that is tagged or attributed to that team's resources.

This is useful for giving engineering teams visibility into their own spend without exposing company-wide billing data.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Only **Admin** users can invite new members, manage roles, and configure integrations.
{% endhint %}

## Setting up Single Sign-On (SSO)

Quper supports SSO via SAML 2.0. To enable SSO for your workspace:

1. Go to **Settings → Security → Single Sign-On**
2. Select your identity provider (Okta, Azure AD, Google Workspace, or custom SAML)
3. Enter your IdP metadata URL or upload the metadata XML
4. Map your IdP group attributes to Quper roles
5. Test the connection, then enable SSO enforcement for your domain

{% hint style="info" %}
Once SSO enforcement is enabled, all users with your company domain must sign in through your identity provider. Password-based login is disabled for those users.
{% endhint %}

## Recommended onboarding order

For most teams, we recommend this order when setting up Quper for the first time:

1. **Connect integrations** — Get all cloud providers and data platforms connected before inviting the wider team
2. **Invite FinOps lead or admin** — This person configures budgets, tags, and governance policies
3. **Invite platform/engineering leads** — Give them Editor access so they can view anomalies and apply recommendations for their services
4. **Invite finance stakeholders** — Viewer access is typically sufficient for finance teams reviewing spend reports
5. **Invite the wider team** — Use team-scoped access to give individual squads visibility into their own spend

## What's next?

{% content-ref url="/pages/N4tcuOR4EmJ5TdaBrFli" %}
[Overview](/integrations/integrations.md)
{% endcontent-ref %}

{% content-ref url="/pages/UMIgTjQ7De2ZY3olDD5n" %}
[Role-Based Access Control (RBAC)](/settings/rbac.md)
{% endcontent-ref %}

{% content-ref url="/pages/qh9vGFz6N3BP0O9XQjac" %}
[Alerts & Notifications](/settings/alerts.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.quper.co/get-started-with-quper/onboarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.