Permissions
Permissions specify user access to data planes, capabilities, and applications. You can assign one or more permissions to individual users, teams, or IdP Groups based on your business needs.
Control Plane Permissions
| Permission | Description |
|---|---|
| Owner |
Owner with this permission can:
|
| Team Admin |
Team admin with this permission can:
|
| View permissions | Users with this permission can view details of assigned permissions to other users by navigating to the User Management > Permissions tab. |
| IdP Manager | User with this permission can configure Single Sign-on for the enterprise from the User Management > Configure SSO page. |
| Data plane Manager |
Users with this permission can:
|
Data Plane and Capability Permissions
| Permission | Description |
|---|---|
| Capability Manager |
Users with this permission can:
|
| Application Manager |
Users with this permission can:
|
| Application Viewer |
Users with this permission can:
|
Product Permissions
Users can be granted either READ (view-only) or WRITE (full management) access to specific domains in Control Tower data plane, ensuring that they can only interact with resources according to the permissions assigned. For more information, see Role-Based Access Control (RBAC) for Domains in Control Tower.
Namespace Level Permissions
Application Manager and Application Viewer permissions can optionally be scoped to a specific namespace within a Kubernetes data plane. This enables multi-team environments where each team manages applications only in their assigned namespaces. You can select the one of following checkboxes also to apply changes for multiple namespaces.
-
All current and future capabilities and namespaces: Selects all capabilities AND all namespaces for this data plane.
-
Apply selected namespace permission to all current and future capabilities: Applies the currently selected namespaces across all capabilities at once.
-
All current and future namespaces: This grants access across all current and future namespaces for that capability and the data plan.
Namespace Permission Scoping Combinations
| Scope | Capability | Namespace | Access |
|---|---|---|---|
| Data Plane level | All | All | All applications in all namespaces |
| Capability-scoped | Specific (for example, BW) | All | All applications for that capability across all namespaces |
| Namespace-scoped | All | Specific (for example, ns-team-a) | All applications in that namespace regardless of capability |
| Capability + Namespace | Specific (for example, BW) | Specific (for example, ns-team-a) | Only applications for that capability in that namespace |
TIBCO Developer Hub does not require namespace-level permissions. It only shows "Grant Application Manager/Viewer permission" without a namespace picker. Only capabilities that deploy applications into Kubernetes namespaces (BW5, BW6, Flogo) display the namespace picker.
For more information, see Managing Namespaces.