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.

Illustrative access by role
RoleCompany overviewCustomer dataFinancial dataPeople dataInvestor reportingPrivate executive notes
Founder or CEOFull accessFull accessFull accessFull accessFull accessFull access
Team memberLimited accessLimited accessNo accessNo accessNo accessNo access
Finance leaderFull accessLimited accessFull accessLimited accessFull accessNo access
Board memberFull accessNo accessLimited accessNo accessFull accessNo access
InvestorLimited accessNo accessLimited accessNo accessLimited accessNo 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 us

Questions?

Talk to us about governance.

Request a demo and ask us anything about permissions, approvals and audit trails.

Request a demo