Docs / Set up your org

Creating your organization

Your organization is the top-level home for everything in REEZN: your projects, members, teams, templates, and the norms and safeguards library. AI generation is configured here too, once, for the whole org.

The person who creates the org becomes its first admin automatically; no one has to grant it. That admin can do everything: configure AI, invite people, create projects and services, and manage norms, safeguards, templates, and personas. As the founder, you start with the full set of keys.

Getting to the wizard

Create an account and sign in. If your email isn’t already part of an org, and you haven’t been invited to one, REEZN shows a choice: create a new organization or join an existing one. Choosing “Create an organization” starts a short onboarding wizard.

If a teammate has already set up your org, don’t create a second one; ask an admin to invite you by email instead. You join their org the first time you sign in with that address, with the role they assigned.

The four onboarding steps

The wizard walks you through the essentials in four steps. None of these choices are permanent; every one of them can be changed later from settings, so you can move quickly and refine afterward.

Organization: name your org. This is just the display name; you can rename it anytime from org settings.
AI provider: choose a provider, paste its API key, and pick a model. This is what powers analysis and canvas generation for the whole org. Keys are stored securely and never shown again after you save.
Invite team: optionally invite teammates by email and assign each a role. This step is explicitly skippable, with a “Skip for now” button that lets you move on and add people later from org settings.
First project: name your first project (a business domain like Billing or Identity) so you have somewhere to start working. An optional one-line description rounds it out.

The first project created here is just a name and description. Adding services, connecting a GitHub repo, and choosing a review policy come later, on the project itself; the wizard keeps this step deliberately light.

The minimum to start generating

Only two things truly matter up front: a name for the org, and an AI provider with a working key, since that is what every analysis and canvas is generated from. Inviting teammates is optional, and even the first project can wait (leave its name blank and you simply land on your org home instead of inside a project). Everything skipped is a few clicks away in settings.

When you finish the wizard, REEZN creates the org, sends any invites you entered, and drops you straight into your first project (or your org home if you skipped the project), ready to create a feature.

Changing anything later

Nothing here locks you in. As an admin, you can revisit every choice from settings:

Rename the org from Org settings.
Switch AI provider, key, or model, and set a different model per task, from Org settings → AI.
Invite more people, change roles, and grant project access via teams from Org settings → Members and Teams.
Add services, connect repos, and tune the review policy from each project’s settings.

Why this exists

A single org is the unit everything else hangs off: projects, people, standards, and one shared AI configuration. Making the creator the first admin, rather than asking for it, means a brand-new team can be productive in minutes, and keeping every onboarding choice editable means you’re never punished for a quick first pass.