Start For Free
Skip to content
Security

Control Who Sees What
And See What Changed

Every workspace lives at its own address with its own members. Roles and private projects decide who sees what, and an audit log shows who changed it.

Members

Private project
  • SarahOwner
  • MarcusAdmin
  • AlexMember
  • Jordan (contractor)Viewer
How it works

Access, History
And Encryption

The controls admins ask about on a demo call, built in from the Free plan up.

Roles That Fit The Org

Owner, admin, member and viewer at the workspace, and admin, member and viewer per project. A private project is visible only to admins and the people you add, and contractors can join as viewers who see only public projects and the ones you grant.

  • Workspace and project roles
  • Private projects for sensitive work
  • Custom roles on Enterprise

Members

Private project
  • SarahOwner
  • MarcusAdmin
  • AlexMember
  • Jordan (contractor)Viewer

A Workspace Audit Log

Admins can search a log of creates, updates and deletes across work items, comments, pages, files, time logs and settings, with who made each change, when, and the old and new values.

  • Search by person or action
  • Old and new values for changed fields
  • Invites, role changes and billing events too

Audit log

  • Sarah changed status of NBX-231To Do → In Review2m
  • Marcus updated priority of NBX-218Medium → High14m
  • Alex deleted page Old launch notes1h
  • Sarah invited jordan@agency.ioas Viewer3h

Zero-Knowledge Pages

Password-protected pages are encrypted in the browser with AES-256. The password never reaches the server, so nobody without it can read the page, NoaBox staff included.

  • Encrypted in the browser
  • On Pro and Enterprise

Protect this page

Team

Who can open it

SBMRALDHJMPLDV
Password••••••••
EncryptionZero-knowledge
CancelSave

Roles, private projects, the audit log and session control are on every plan. Password-protected pages are on Pro and Enterprise; custom roles on Enterprise.

The details

And The Small Things
That Add Up

Your own subdomain

Every workspace lives at its own address, with its own members, projects and integrations.

Active sessions

See every signed-in device and revoke any of them. Admins can force a sign-out for a member.

Email code or Google sign-in

Sign in with a one-time code sent by email, or with Google.

AI you can budget

Set a monthly credit cap per member or switch AI off for anyone. Members are alerted at 80% and 100%.

Noa acts with your permissions

Noa only sees what the person asking can see, and in Slack it changes a work item only when asked.

Secrets handled carefully

Slack tokens are encrypted at rest, GitHub webhooks are signature-checked, and GitHub tokens are short-lived.

FAQ

Questions, answered

  • Owner, admin, member and viewer roles decide what people can do. Private projects are visible only to admins and the people you add; public projects are visible to every member of the workspace. Admins can search the audit log, see active sessions and sign anyone out.

  • With a one-time code sent by email, or with Google. SAML single sign-on isn't available yet.

  • You can invite them as a viewer with access to specific projects. Keep sensitive projects private: viewers can still read public projects in the workspace.