Skip to content

Commit 0649617

Browse files
committed
change the placement of Support user permissions in manage users and teams
1 parent da6f5fb commit 0649617

File tree

1 file changed

+23
-24
lines changed

1 file changed

+23
-24
lines changed

docs/sso-rbac/users-and-teams/manage-users-teams.md

Lines changed: 23 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -53,30 +53,6 @@ These roles can be used to define specific permissions for assets in your softwa
5353
For example, you can define that all `Members` can create new entities from a specific blueprint, while only `Moderators` can edit them.
5454
For more information and examples, see the [catalog RBAC](/build-your-software-catalog/set-catalog-rbac/) section.
5555

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-
8056
## Ownership & user management
8157

8258
After creating a Port account, two <PortTooltip id="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
449425
Service accounts can easily be disabled at any time. To disable a service account, update it's `status` property to `Disabled`.
450426
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`.
451427

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.
450+
:::

0 commit comments

Comments
 (0)