Your service desk does not need SAP_ALL
One of the quieter risks in SAP operations is how often broad access is granted simply because it is the easiest way to let someone see something.
Visibility and privilege are different things
The service desk needs to know an alert fired. They do not need to restart an instance. A customer contact needs to see availability for their systems, not anyone else's. A contractor needs their own work and nothing more.
When the only way to give visibility is to give privilege, organisations face a bad choice: restrict visibility and keep production rights holders answering "is it down?" all day, or widen privilege and accept the risk.
What good access design looks like
- Read separated from actSeeing an alert and executing a command are different permissions.
- Credentials never shownMost people who need the status never need a password.
- Scoped by customerService providers keep each client's data within that client's boundary.
- Everything attributableEach privileged action records who, from where and with what result.
How FCC handles access
Eight built-in roles
From platform owner to read-only alert monitoring.
Granular permissions
Per-action permissions behind every screen and every API call.
Per-customer isolation
For service providers running several clients on one platform.
Audit trail
Who did what, from where, and with what outcome.
The point is not more bureaucracy. When access matches the job, you can safely give more people the visibility they need.
Go deeper
Common questions
Can the service desk triage without execution rights?
Can roles be adjusted?
Give more people visibility, with less privilege.
We will map FCC's roles onto your team's responsibilities in a short session. FCC is in Beta.
"SAP" and SAP product names are used descriptively. Farrenio Cloud Control is a Farrenio product and implies no partnership with or endorsement by SAP.