As teams grow, so does the need to share access—without giving away too much control.
Today, we’re introducing a new role in GrapheneDB: Read Operator. This role is designed for team members who need visibility into your environments, but shouldn’t be able to make changes.
It’s a small addition, but one that solves a very real problem—and it’s available right away.
What a Read Operator Can Do
A Read Operator has full visibility, but no control.
They can:
- View logs to troubleshoot issues
- Inspect metrics to understand system performance
- Access connection settings for integration and debugging
This makes the role especially useful for:
- QA and testing teams
- support engineers
- external collaborators
- product or analytics stakeholders
What a Read Operator Cannot Do
Just as important as what they can do is what they can’t. Read Operators are limited to read-only access and cannot perform any actions in the Console that result in changes, including:
- Launching any operation on databases
- Modifying configurations
- Adding any service, like snapshots or replicas
In short, they can observe everything—but they can’t touch anything.
Available Now
You can start using the Read Operator role immediately.
- Update the role of existing organization members to Read Operator
- Assign it when inviting new members to your organization
No additional setup is required—it’s ready to use as part of your current access management workflow.
Learn More
If you’d like to see how this role fits into the full permissions model, you can check out our documentation here