Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/en/cloud/concepts/spaces/profiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,9 +26,9 @@ A profile is visible to:
- the Organization Admins of its organization, and
- members of any team assigned to a workspace the profile is assigned to.

The owner always sees their own profile, whether or not it is in a workspace and even without the **View Profiles** permission. Organization Admins and workspace members also need **View Profiles**. Provider Admins do not see profiles automatically. Seeing a profile does not give you access to its linked connections, which keep their own access rules.
The owner always sees their own profile, whether it is in a workspace and even without the **View Profiles** permission. The person a profile represents can also read it, so when an admin creates a profile for you, it appears in your profile list and you can open it, even without **View Profiles**. That is read-only: changing the profile, linking connections and seeing its connections still follow the rules on this page. Organization Admins and workspace members also need **View Profiles**, unless they are the owner or the person the profile represents. Provider Admins do not see profiles automatically. Seeing a profile does not provide access to its linked connections, which keep their own access rules.

A profile that is in no workspace is visible only to its owner and the organization's admins. What you can change is never wider than what you can see: a profile you cannot see answers 404, the same as one that does not exist.
A profile that is in no workspace is visible only to its owner, the person it represents, and the organization's admins. What you can change is never wider than what you can see: a profile you cannot see answers 404, the same as one that does not exist.

## Owner and succession

Expand All @@ -40,7 +40,7 @@ When the owner's account is deleted, the profile passes to the earliest Organiza

| Permission | Allows |
| --- | --- |
| View Profiles | Listing and reading the profiles you can see, and their connections. Owners read their own profiles without it. |
| View Profiles | Listing and reading the profiles you can see, and their connections. Owners read their own profiles without it, and the person a profile represents can read that profile without it. |
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved
| Create Profile | Creating a profile in an organization |
| Edit Profile | Editing any visible profile, transferring its ownership, and linking or unlinking connections |
| Delete Profile | Deleting a profile |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Each action needs the permission named beside it. A profile you cannot see, one
}
```

`organizationId` and `name` are required. You become the owner unless you send `owner`. `owner` and `userId`, when sent, must each be a signed-in member of the organization, or the request answers 400. A new profile is in no workspace, so only you and the organization's admins can see it until you assign it.
`organizationId` and `name` are required. You become the owner unless you send `owner`. `owner` and `userId`, when sent, must each be a signed-in member of the organization, or the request answers 400. A new profile is in no workspace, so you, the user it represents, and the organization's admins can see it until you assign it.

## Edit or transfer a profile

Expand Down
Loading