Set up your workspace
Configure your brand, theme, sources, and defaults so everything you generate looks and sounds like your organization.
A workspace holds your people, content, settings, and data. Most organizations use one workspace; large enterprises sometimes run separate workspaces for internal training and customer education. Spend a few minutes on the settings below before inviting anyone, because they shape everything Nucleus OS generates.
Checklist
| Setting | Why it matters | Where to read more |
|---|---|---|
| Account and profile | Your name, email, and sign-in method. Open it from your avatar in the dashboard. | Security settings |
| Plan and credits | Determines your monthly credit pool for AI generation. Found under Usage & Billing in your profile. | Billing and credits |
| Brand voice and visual style | Tone, terminology, colors, and fonts applied to every lesson. | Brand voice |
| Source connections | Lets authors pull material from Google Drive, Notion, and other tools. | Importing sources |
| Single sign-on | Lets people sign in with your identity provider. | SAML SSO |
| HR data | Powers automatic enrollment, due dates, and manager reporting. | HRIS sync |
Brand and appearance
Upload your logo and set brand colors so courses, certificates, and emails match your identity. Add your style guide or a few representative documents to the brand library so the authoring assistant learns your tone and terminology once and applies it everywhere.
Light and dark mode
The dashboard supports light and dark themes. Use the theme toggle in the sidebar to switch; your choice is remembered on this device.
Connect your sources
Open Connectors from the sidebar to see the available integrations. Connecting a knowledge source (for example Google Drive or Notion) means authors can build courses from the documents your teams already maintain, and Nucleus OS can propose updates when those documents change.
Decide on your structure
Before you build many programs, agree on a few conventions with your team:
- Naming. A short, consistent pattern such as
Team · Topic · Levelmakes catalogs and reports easier to read. - Ownership. Every course should have an owner who approves changes and handles review-gate flags.
- Audiences. Write down which roles, teams, and locations each program is for. These become your enrollment rules.