# Managed policies and preset roles

The policies {{product}} maintains for you, what each grants, and the preset roles that attach them to new members.

A **managed policy** is a policy Deutsche Cloud maintains. You attach it like any other policy, but you
cannot edit or delete it. Its document is not stored in your organization: it is the platform's
current definition of that name, read every time it is evaluated. When a service gains an action,
every organization's managed policies include it from the next platform update.

To keep a permission set fixed, create a custom policy and copy a managed policy's document into it
(the **Templates** tab of **Create policy** does this).

## The managed policies

| Name                      | Grants                                                                                                          |
| ------------------------- | --------------------------------------------------------------------------------------------------------------- |
| `AdministratorAccess`     | `*` on `*`: every action, including identity and billing.                                                       |
| `PowerUserAccess`         | Every action except those of IAM and billing.                                                                   |
| `DeveloperAccess`         | Every action except those of IAM and billing, plus billing reads.                                               |
| `ReadOnlyAccess`          | Every read across the services, except sensitive reads and reads that cost money or send data to a third party. |
| `<Service>FullAccess`     | Every action of one service, such as `Ec2FullAccess` or `RdsFullAccess`.                                        |
| `<Service>ReadOnlyAccess` | The same, for one service, such as `KmsReadOnlyAccess`. A service with no such reads has none.                  |

All of them allow their actions on `*`. A **sensitive read** hands over secret material or source
code, such as revealing a secret's value or downloading a repository; no read-only policy includes
one.

`GET /iam/api/managed-policies` lists every managed policy with its document.

## Preset roles

A preset role is a member's organization role. It attaches its managed policy to the member's IAM
user when they join, and changing the role on **Members** swaps that policy for the new role's.
**Identity** → **Roles** lists them under **Preset roles**.

| Preset    | Attaches              | Given by                                               |
| --------- | --------------------- | ------------------------------------------------------ |
| Owner     | `AdministratorAccess` | Creating the organization; not by invitation           |
| Admin     | `AdministratorAccess` | An invitation, a first single sign-on or a role change |
| Member    | `DeveloperAccess`     | An invitation, a first single sign-on or a role change |
| Viewer    | `ReadOnlyAccess`      | An invitation, a first single sign-on or a role change |
| Billing   | `BillingFullAccess`   | An invitation, a first single sign-on or a role change |
| No preset | nothing               | An invitation only                                     |

An admin and the owner hold the same policy; only the owner can transfer or close the
organization. Members who joined as Admin before 2026-11-19 hold `PowerUserAccess`; they are given
`AdministratorAccess` too, and a role change away from Admin detaches both. To give a member more
or less than a preset, attach or detach policies on their IAM user or add them to a group; the
Members page then shows **Custom permissions**.

## Related

- [Attach a policy](attach-a-policy.md)
- [Create a policy](create-a-policy.md)
- [Invite a person](invite-a-person.md)
