Overview
There are two levels of rules that determine what you can do in Observability.
Permissions - Whether you can manage a job (edit, delete, configure) depends on whether your license and team use Role-Based Access Control (RBAC).
When using RBAC: anyone holding the
Manage Observability jobspermission can access the jobs.When not using RBAC: the job's creator, team owners, or anyone with delegated access to the org connection behind the job can access the jobs.
Org Access Permissions - Observability needs the org permissions outlined here to be able to access your org.
⚠️ Only teams on Automation Starter (or higher) and Deployment Teams have RBAC. You can read more on RBAC here.
Permissions
Whether you can configure a job is governed by the permissions that your team uses. This is different between teams that use RBAC and non-RBAC permission policies.
When using RBAC permissions, you can set this permission in the Role assigned to users that determines access to the Observability feature:
When not using RBAC permissions, there is a setting under the non role based Gearset Permissions
Configuring Error Monitoring or Access Monitoring during job setup always requires ownership of the connection behind the job, even under RBAC with Manage Observability jobs granted.
For team-shared connections, the team owner is treated as the connection owner.
Org Access Permissions
Live-org features (Access Monitoring and Async Apex Executions) reads data directly from the connected org, so they are gated by your delegated permissions on that connection rather than by the permission model:
Delegated access to the org - can view Access Monitoring and Async Apex Executions.
No delegated access - cannot view Access Monitoring or Async Apex Executions.
Team owner on a team-shared connection - treated as having access; can view both.
Team owner on a connection that is not team-shared - follows the delegated access above. Team ownership alone grants nothing on a connection that has not been shared to the team.
Frequently asked
Why can I see the job and its errors, but not Access Monitoring or Async Apex Executions?
Access Monitoring and Async Apex Executions read live data from the connected org, so they need at least a delegated access level of Compare to the org. Ask the connection's owner or your team owner to delegate Compare access or higher.
Why can't I edit or delete a job I can see?
Under RBAC, editing and deleting require the Manage Observability jobs permission. Without RBAC, only the person who created the job, team owners, and the owner of the connection behind it can edit or delete the job.
Being able to view a job does not inherently grant these permissions.
I have Manage Observability jobs - why can't I configure Error Monitoring or Access Monitoring?
Configuring those during setup requires ownership of the connection behind the job, which RBAC does not give to users. Use a team-shared connection (where the team owner counts as the owner), or ask the org connection owner to set it up.