> For the complete documentation index, see [llms.txt](https://docs.firefly.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firefly.ai/getting-started/access-management-rbac.md).

# Access Management (RBAC)

Firefly’s Access Management lets you control who can access specific parts of your cloud environment, which actions they can perform, and which data sources their permissions apply to.

This provides stronger security, clearer governance, and flexibility as your teams scale.

## Overview

Access Management introduces a role-based permission model across the Firefly platform.

With RBAC you can:

* Assign fine-grained permissions for every part of the platform
* Control access by Users, Teams, and Service Accounts
* Generate API keys with scoped permissions
* Limit access to specific cloud integrations or allow full-tenant access
* Enforce least-privilege access across your organization

RBAC applies to all major Firefly areas, including Inventory, Governance, Integrations, Notifications, IaC Explorer, and more.

***

## Access Management Menu

Access Management consolidates identity and access controls into one place:

**Access Management →**

* Users
* Teams
* Service Accounts
* Roles
* API Keys (per Users, Teams, Service Accounts)

***

## Key Concepts

### Roles

A role defines a set of permissions.

Roles can be assigned to:

* Users
* Teams
* Service Accounts

#### Default roles

Every tenant includes two built-in roles:

* **Admin** – Full access to all scopes and actions.
* **Viewer** – Read-only access to all supported areas.

Admins can create additional custom roles.

***

### Permission modes

When creating or editing a role, each role can operate in one of three modes:

#### Full Access (Admin)

Grants all available permissions across all data sources.\
All actions are enabled, and all integrations are accessible.

#### Read-only

Users can view everything but cannot create, update, delete, or remediate.

#### Limited Access (Scoped)

Fully customizable, including:

* Specific integrations (for example, specific AWS/GCP/Azure accounts)
* Specific actions (for example, “View Inventory” but not “Delete Asset”)

This is ideal for least-privilege or team-specific access.

***

### Workflows permissions

Access to Firefly Workflows is also managed through roles. A role can be scoped to specific **Workflows projects**, and for each project you choose exactly what the role can do:

* **View** — see the project, its workspaces and their runs.
* **Run** — trigger plans.
* **Apply** — approve and apply runs.
* **Manage state** — manage the workspace's remote state.

The same permissions are enforced across the **UI, the API and the Terraform CLI**, so there is no gap between what a user can do in each surface.

**Migration from project assignments:** access to Workflows projects used to be managed by assigning users directly to each project. Existing assignments were migrated to roles automatically:

* **Project Users** received full access to their projects, including sub-projects and the workspaces in them.
* **Account Admins and Viewers** keep access to all projects.

> **Note:** The **Default Project** is visible only to Admins and Viewers. If non-admin users work in Default Project workspaces, add the Default Project to their role so they can see those workspaces.

Project-level scoping for **Guardrails** and for **workspace run details** (logs, plan output, cost and scan results) is not yet supported; Guardrails are managed by Admins across the account.

***

### Service accounts

Service accounts let you create identities for automation tools or CI/CD systems without tying them to human users.

Each service account can have:

* Roles
* API keys

***

## Migration from legacy permissions

Firefly automatically migrates existing tenants into the new RBAC model.

### What happens during migration

* Existing Admins become **Admin** role users.
* Existing Viewers become **Viewer** role users.
* Legacy tenant-level API keys are migrated into **Service-Account-level API keys**.
* All migrated keys retain their original capabilities.

***

## Best practices

* Use **Teams** to manage access at scale.
* Use **Service Accounts** for automation instead of human API keys.
* Start with **Read-only** roles for new users.
* Use **Scoped roles** for vendors, temporary users, or least-privilege access.
* Rotate API keys regularly, especially after migration.
* Review role assignments periodically (for example, quarterly).

***

## Limitations

* Only **Admins** can access the **Access Management** screen.
* Only **Admins** can manage **Integrations**, including create, update, and delete operations.
* Legacy **API keys** will be migrated and linked to a specified **Service-Account**.
* **Workflows:** Guardrails and workspace run details (logs, plan output, cost and scan results) cannot yet be scoped per project.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.firefly.ai/getting-started/access-management-rbac.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
