Organizations and onboarding
Create, select, and scope the organization whose compliance data you are operating.
Organizations and onboarding
Noru currently uses organizations (also called workspaces in parts of the interface) as the primary tenant
boundary. There is no separate /workspaces management page; use organization selection and Settings.
Choose organization (/org/select)
Select an organization you belong to or create a new one. The selected organization controls every downstream query and write. If access to the previously active organization was removed, Noru sends you here to choose one you still belong to.
Always confirm the active organization before uploading evidence, connecting a data source, generating a report, or publishing a trust center. Cross-organization movement is not an ordinary editing operation.
Create and onboard (/org/new)
The onboarding guide creates or resumes the organization baseline. It gathers organization context, framework selection, and setup inputs used to seed the initial program. If an organization is already onboarded, the route returns to the dashboard.
Choose frameworks and scope based on real customer, contractual, certification, or regulatory needs. Generated controls and policies are starting content and must be tailored, owned, evidenced, and approved.
Authentication support pages
/sign-inand/sign-uphandle authentication./get-startedhandles the public entry/onboarding hand-off./mfa-requiredhelps a member satisfy an organization-wide MFA requirement./checkout-successconfirms billing checkout and then returns to the requested in-app destination.
These pages support access and onboarding; they do not hold compliance records themselves.