You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/sso-rbac/users-and-teams/manage-users-teams.md
+23-24Lines changed: 23 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,30 +53,6 @@ These roles can be used to define specific permissions for assets in your softwa
53
53
For example, you can define that all `Members` can create new entities from a specific blueprint, while only `Moderators` can edit them.
54
54
For more information and examples, see the [catalog RBAC](/build-your-software-catalog/set-catalog-rbac/) section.
55
55
56
-
## Support user permissions
57
-
58
-
<SupportUserPermissions/>
59
-
60
-
### Access duration
61
-
62
-
Support user access is enabled by default.
63
-
You can define how long this access will be valid: **1 week**, **1 month**, **1 year**, **Permanent access (default)**.
64
-
65
-
### Support user capabilities
66
-
67
-
Support users can be created with the following restrictions:
68
-
69
-
-**Read-only access** - can be created as `read-only` users.
70
-
-**Admin/edit access** - can be created as `admin` users, their actions will appear in your organization's audit log. This requires both Port manager approval and customer approval via the support user permission process.
71
-
72
-
:::info Emergency access
73
-
74
-
In critical situations, Port can request emergency access to your organization even if support user permissions are disabled. This requires:
75
-
76
-
1.**Organization approval** - the organization admin must approve the emergency access request.
77
-
2.**Port approval** - Internal Port approval process.
78
-
:::
79
-
80
56
## Ownership & user management
81
57
82
58
After creating a Port account, two <PortTooltipid="blueprint">blueprints</PortTooltip> will be automatically created in your [data model](https://app.getport.io/settings/data-model) - `User` and `Team`.
@@ -449,3 +425,26 @@ Port service accounts are treated like any other users and extend the same RBAC
449
425
Service accounts can easily be disabled at any time. To disable a service account, update it's `status` property to `Disabled`.
450
426
Disabled service accounts can no longer generate new API tokens or use existing ones. Disabled service accounts can be re-enabled at any time by updating the `status` property back to `Active`.
451
427
428
+
## Support user permissions
429
+
430
+
<SupportUserPermissions/>
431
+
432
+
### Access duration
433
+
434
+
Support user access is enabled by default.
435
+
You can define how long this access will be valid: **1 week**, **1 month**, **1 year**, **Permanent access (default)**.
436
+
437
+
### Support user capabilities
438
+
439
+
Support users can be created with the following restrictions:
440
+
441
+
-**Read-only access** - can be created as `read-only` users.
442
+
-**Admin/edit access** - can be created as `admin` users, their actions will appear in your organization's audit log. This requires both Port manager approval and customer approval via the support user permission process.
443
+
444
+
:::info Emergency access
445
+
446
+
In critical situations, Port can request emergency access to your organization even if support user permissions are disabled. This requires:
447
+
448
+
1.**Organization approval** - the organization admin must approve the emergency access request.
449
+
2.**Port approval** - Internal Port approval process.
0 commit comments