Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nudj.cx/llms.txt

Use this file to discover all available pages before exploring further.

Every Nudj customer starts at the organisation level. Organisations own one or more communities, team members, RBAC roles, branding, domains, and integrations. See Organisations vs Communities for the mental model.

Single-step creation

Nudj consolidated organisation creation into one form. You pick a name, slug, and optional logo, and save — no multi-screen wizard.

Sign up

Go to admin.nudj.cx. Authenticate with Google, Azure, or email magic-link.

Fill the org form

Enter your organisation name (shown in the top nav), a URL slug (used in /{orgSlug} routes), and optionally upload a logo. The logo appears in the admin top nav and on member-facing landing pages.

Land in Create Community

After saving, Nudj redirects you directly to the Create Community screen. Every org needs at least one community to do anything useful. See Community Setup.
If you already belong to an org (e.g. a teammate invited you), you’ll be routed straight to that org’s dashboard — no creation step.

What you configure next

Once the org exists, head to Organisation Settings to tune the rest:

General & Branding

Org name, logo, landing-page header, timezone.

Team Members & Roles

Invite collaborators and assign Viewer / Moderator / Manager / Admin / SuperAdmin.

Domains

Attach custom member-facing domains.

Login Methods

Configure standard and enterprise SSO providers.

The org switcher

If your account belongs to multiple orgs, the top-nav org switcher lets you jump between them. Each org has its own isolated cookie, roles, and content — switching does not leak data between orgs. When you switch org, Nudj lands you on that org’s dashboard (/{orgSlug}) — not on a specific community. Pick a community from the community dropdown to drill in.

Multi-community orgs

You can run many communities under one org (e.g. a parent brand with regional sub-communities, or a SaaS customer with one community per enterprise tenant). Team members with org-level roles see every community; community-scoped roles only see the communities they’re assigned to. See Roles & Permissions.
Start with one community. Spin up more only when you have distinct audiences or programs — not as a substitute for categories.