- Home
- Security
Governance is part of the architecture
Who can see what, who can approve what, and what happened and when. Create Build Optimize OS builds these questions into the system instead of adding them afterwards.
Role-based permissions
Everyone sees what they should.
Access follows the role. This matrix is illustrative: your own roles and access levels are set up for your company.
| Role | Company overview | Customer data | Financial data | People data | Investor reporting | Private executive notes |
|---|---|---|---|---|---|---|
| Founder or CEO | Full access | Full access | Full access | Full access | Full access | Full access |
| Team member | Limited access | Limited access | No access | No access | No access | No access |
| Finance leader | Full access | Limited access | Full access | Limited access | Full access | No access |
| Board member | Full access | No access | Limited access | No access | Full access | No access |
| Investor | Limited access | No access | Limited access | No access | Limited access | No access |
- Full access
- Limited access
- No access
Investor visibility
Investors and funds see permissioned portfolio KPIs and reporting, and nothing beyond what the company chooses to share.
Approvals and audit trails
Meaningful actions go through approvals, and approvals, changes and recommendations are recorded, so every action is traceable.
Private executive context stays separate
Private executive context is kept separate by default, so it does not leak into views or NOVA answers meant for other people.
Human-approved AI
NOVA recommends and prepares. People approve meaningful execution, and NOVA only uses data the person asking is authorized to see.
Detailed security documentation is available on request.
Contact usQuestions?
Talk to us about governance.
Request a demo and ask us anything about permissions, approvals and audit trails.