Roles and Access Model

Atlanta, USA

Cloud2BR OSS - Learning Hub

Last updated: 2026-08-04

---

References

• Manual onboarding
• Contact support

Objective

Define role ownership and least-privilege access boundaries before broad adoption.

Security Copilot role model

Role	Typical responsibility
Owner	Capacity, plugin controls, environment-level governance
Contributor	Operational use, content execution, and approved configuration tasks
Analyst	Daily investigations, prompts, and workflow execution

Access governance priorities

1. Ensure at least two owners for continuity.
2. Separate capacity administration from day-to-day analysis roles.
3. Document emergency escalation roles for service-impacting issues.
4. Align support-case permissions with operational responsibilities.

Required controls

• Periodic role review.
• Privileged action logging.
• Plugin publishing restrictions.
• Support escalation runbook ownership.