Skip to content

Add documentation for Custom Roles feature#4293

Draft
brianmacdonald-temporal wants to merge 1 commit intomainfrom
custom-roles
Draft

Add documentation for Custom Roles feature#4293
brianmacdonald-temporal wants to merge 1 commit intomainfrom
custom-roles

Conversation

@brianmacdonald-temporal
Copy link
Contributor

@brianmacdonald-temporal brianmacdonald-temporal commented Mar 13, 2026

What does this PR do?

Adds documentation for the Custom Roles feature

Notes to reviewers

┆Attachments: EDU-6050 Add documentation for Custom Roles feature

@vercel
Copy link

vercel bot commented Mar 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Mar 13, 2026 7:11pm

Request Review

@github-actions
Copy link
Contributor


Using Custom Roles with [Service Accounts](/cloud/service-accounts) can make them more secure for automation purposes.

## Defining Custom Roles
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[new information] We have limits set for pre-release that need to clarify:

  • Each account can create up to 25 custom roles, while UI may display at most of 100 custom roles.
  • No hard limit on number of permission actions per custom role
  • A max of 10 custom roles can be assigned per principal (e.g. user)
  • A max of 20 specific resources (e.g. NS) per custom roles total. Note that apply to ALL resources is still supported even if there are more than 20.

Slack thread for reference: https://temporaltechnologies.slack.com/archives/C09FNFWRW0L/p1773412536252889

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add to https://docs.temporal.io/cloud/limits and link from here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Separately, we should also add modifying and deleting a customer role workflow
and explicitly mention what permission role is needed for these actions: today only account owner & global admin can create/modify/delete a customer role. We don't support custom role delegation e.g. create a role to allow someone for managing custom role (hope this isn't confusing :D)

You can scope roles to:
* All resources of a given type
* Specific resources by explicit ID list
* Resource subsets
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is a resource subset?

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

Temporal Cloud currently offers a fixed set of predefined [account-level roles and Namespace-level permissions](https://docs.temporal.io/cloud/users#account-level-roles).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Temporal Cloud currently offers a fixed set of predefined [account-level roles and Namespace-level permissions](https://docs.temporal.io/cloud/users#account-level-roles).
Temporal Cloud offers a set of predefined [account-level roles and Namespace-level permissions](https://docs.temporal.io/cloud/users#account-level-roles).

Comment on lines +24 to +25
These roles are sufficient for many Temporal use cases, but not for supporting enterprise-grade access models
that require least privilege, delegation, and automation-safe permissions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
These roles are sufficient for many Temporal use cases, but not for supporting enterprise-grade access models
that require least privilege, delegation, and automation-safe permissions.
These roles are sufficient for many Temporal use cases, but can't cover all combinations of least privilege, delegation, and automation-safe permissions often required in large enterprises.

Trying to sound less negative about the fixed roles

## What are Custom Roles?

Custom Roles enable you to define your own roles as bundles of permission primitives (operations/actions)
scoped to applicable resources (namespaces, projects, account objects) and assign them to any
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intentional projects mention?


Use Custom Roles if you want more fine-grained authentication than Temporal Cloud's predefined roles and permissions provide.

Use Custom Roles if your access model requires the Principle of Least Privilege or delegation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds a little funny - all access models SHOULD adhere to this. It's more when there's a significant gap between what least privilege means in the user context and what our fixed roles offer.


Using Custom Roles with [Service Accounts](/cloud/service-accounts) can make them more secure for automation purposes.

## Defining Custom Roles
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add to https://docs.temporal.io/cloud/limits and link from here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants