Access
Every app sits behind company sign-in. By default only the owner can open it. The access model is explained in Access & security.
tc access
Shows who can open the app. Same as tc access show.
tc access [show] [--project NAME] [--json]
Output
expenses: the owner + listed people and groups
owner Isabel Moreno <isabel.moreno@contoso.com>
member group Operations
role approver: user henrik.larsen@contoso.com
For team and department, the live rule is resolved too:
budget: the owner's team (their manager's direct reports)
team 7 people reporting to Dana Whitfield (live)
JSON: { project, mode, owner, members, roles, live }.
tc access set
Changes who can open the app. Owner, project developers or an admin; audited.
tc access set MODE [--member X]... [--role NAME=X]... [--project NAME] [--json]
| Argument / flag | Description |
|---|---|
MODE | One of the modes below |
--member X, -m | A person or group allowed in (groups mode). Repeat it. Replaces the current list. |
--role NAME=X | Give app role NAME to X. Repeat it. Roles reach your app in user.roles and in SQL as tc.has_role(). |
X is a user email, a group name ("Finance - FP&A") or a directory object id.
| Mode | Who can open the app |
|---|---|
only_me | Only the owner (default for new projects) |
team | The owner's team: their manager's direct reports, resolved live from the directory |
department | The owner's department, live |
groups | The owner plus the listed people and groups |
everyone | Everyone in your organization (your company's directory) |
Errors: --role expects NAME=PRINCIPAL; UNKNOWN_PRINCIPAL (unknown person or group); INVALID_ACCESS (for example groups with nobody listed); READ_ONLY if you can't manage the project.
Examples
tc access set everyone -p budget
tc access set groups -m Operations -m kwame.mensah@contoso.com --role approver=henrik.larsen@contoso.com
tc access set department
Was this page helpful?