Getting into the platform

3. Create your organization

Creating an organization takes about two minutes and goes through nobody. There is no approval queue, no activation call and nobody on the other side releasing your account: you finish signing up already as Admin, with full access.

Signing in for the first time

The app lives at orionworkers.com. On the home page, both the "Hire your AI worker" button and the "Sign in" link lead to the same screen — it works for creating an account and for signing in.

You sign in two ways: with your Google account or with your email — and in that case the platform sends a one-time code to your inbox. There is no password to create and none to remember.

The platform also does not ask for your first name, last name, phone or country. What it knows about you in the first second is your email (and the name and photo Google may already have sent).

The two questions at signup

Signing in with no organization, two screens appear — and only two.

1. "Create your organization". It asks for one field: the organization name. No tax ID, address, company size or industry.

2. "What do you want to solve first?" Three buttons, one click:

• "Get an AI manager on WhatsApp" — Orion runs the day-to-day, chases deadlines and brings you what needs your decision.
• "Organize deliverables and the team" — Team priorities per period, each person's contribution, deadlines and per-cycle assessment.
• "Both" — The AI manager running the day-to-day over the work recorded in the system.

That choice decides where you land: whoever answers "Organize deliverables and the team" opens on the deliverables dashboard; the other two answers open on Orion. It is a front-door decision, not a plan you bought — no feature is hidden, and you can change it later. As the screen itself says: "Nothing gets locked — the rest is there whenever you want it."

Neither screen asks for a credit card. What each plan does, and what it costs, is at /pricing.

The country nobody asked about

You never tell it what country you are in. The platform infers it from your browser's time zone and language, at the moment the organization is created:

• a Brazilian time zone (São Paulo, Recife, Manaus, Fortaleza…) or the `pt-BR` language → Brazil, in reais;
• another time zone in the Americas → United States, in dollars;
• a European time zone → dollars;
• no time zone, or one it cannot recognize → no country is asserted, and billing asks when the time comes.

This is not cosmetic: that inference decides which billing account your organization will be charged on — the Brazilian account in R$ or the Canadian one in US$ — and the first purchase locks the organization onto that account. Hence the house rule: the billing screen always shows the currency before charging, and lets you correct it. If you created the organization while traveling, check the currency before you subscribe.

What the platform sets up for you

When you finish signing up, your organization is already set up:

An active organization

created and active on the spot, with the name you gave it.

You as Admin

the highest org role, with access to everything (chapter 5).

A team called "General"

it is already your home team, and you are already its manager. You do not have to create your first team to get started — and you can rename "General" or create others whenever you want.

Your worker record

this is what work plans belong to. Every registered human gets one.

You as the organization's primary contact.

The old manual said that, after creating the organization, "you are not assigned to a team". That stopped being true: you are the manager of General before you touch anything.

"First steps"

On both home screens (the deliverables dashboard and the Orion home screen) there is a card called First steps, collapsed by default, showing a progress ring and "x of y done".

It is not a tour with checkboxes. Every line is derived from the organization's real state, computed on the server: a step is checked because the WhatsApp number is in fact connected, because the deliverables plan is in fact signed — never because someone clicked "got it". Each screen shows the steps that get resolved there:

While a step is pending, it shows why it matters ("No team means nobody to delegate to and nobody to chase"). When every step on one of them is done, the card disappears from there on its own.

A scope detail: First steps only appears for Admins. Whoever joins an already-built organization configures nothing and does not see the list.

See a company running before you decide

On the signup screen there is a shortcut that is easy to miss: "Before you start, see a working sample organization", with the 🎬 button. It drops you inside a demonstration organization — Aurora Digital — with teams, people, deliverables and plans already filled in.

Two things to know: that organization is read-only (the server refuses any write, and it is the same organization every visitor sees), and the way out is a fixed banner at the top of the screen. The shortcut does not appear inside the mobile app.

4. Join an existing organization

If someone already created the organization and you were called into it, the path is short — but it carries a consequence worth reading before you click.

There is no invite code

Let us get this out of the way first, because the old manual said the opposite in five places: there is no invite code. Nobody generates a code, nobody shares a code over WhatsApp, and there is no "join a team" screen where you type something in.

The invitation is always by email, and the person inviting is always an organization Admin — on the Users page, by typing your address. A team manager invites nobody from outside (chapter 5).

From there, what happens depends on a single question: does your email already exist in some organization on the platform?

Path 1 — your email is new here

The Admin registers your email in Users, choosing, right there, your org role, your home team and your role in that team. Your record is created immediately, and you get an email with the sign-in link (if you already have an account at that address, just sign in with it as usual).

You sign in at orionworkers.com with that email and you are already in, with the role the Admin chose. There is no acceptance screen — there is nothing to accept, because your account was born there.

Path 2 — you already belong to another organization

Here the platform takes a different path, on purpose. Since an account belongs to one organization at a time, the Admin cannot create a second record for you: the system creates a pending invitation and sends an email written to explain exactly that.

When you sign in to the app with that email, you see the invitation screen:

> You've been invited — Jane Doe invited you to join Acme Inc. > Joining moves your account to this organization. > [ Join Acme Inc. ] [ Not now ]

Read the notice carefully, because it is literal. Accepting moves your account. The moment you click "Join…":

• you leave the organization you were in, and your access to it ends;
• all your previous team roles are terminated;
• your worker record moves to the new organization;
• your org role is reset to User, and you join as a member of the team named in the invitation.

This is not a context switch you can undo with a click: to go back, someone from the old organization has to invite you again — and you will come back as a User, without the team roles you had.

"Not now" declines the invitation, which disappears. Declining is reversible: the Admin can invite again.

A side effect that confuses newcomers: while there is a pending invitation for your email, the platform will not create a new organization for you. If your intent is to have your own organization and not join the inviter's, decline the invitation first and then use "Or create your own organization".

And an honest check before you accept: if you are today the only Admin of your current organization, nothing blocks your exit. The old organization is not deleted, and the platform promotes the longest-standing person left to Admin — but if nobody is left, it ends up with no active owner. Promote another Admin before you move.

Weekly workload and salary: who fills them in

The old manual told you to "ask your manager" to fill in your weekly workload and your salary. That does not work.

Those fields are HR's: only someone whose org role is Admin or HR can write them — on your profile they appear with a lock 🔒 and, if anyone tries from outside the screen, the server refuses. Your team's manager cannot, unless they also hold one of those two org roles.

It is worth having them filled in: the weekly workload is the basis of effort in the work plan, and compensation is what lets the organization calculate the cost of a deliverable. But the request has a correct address: an Admin or HR.

5. Roles and permissions

This is the chapter that changed the most. The previous manual described this section as "inferred based on standard management-software practices" — and got it wrong on almost every line. It is not inference: these are real roles, with a closed list of values, checked by the server on every request. Below is what the platform does today.

Two layers

Everyone has one org role and, on top of that, one role in each team they take part in. The two layers answer different questions:

Org role

what you reach across the whole company — people records, settings, billing, broad reading. One per person.

Team role

what you can do inside that team — create deliverables, sign plans, assess cycles. One per team, and you can have different roles in different teams.

For reads, the org role is the stronger one: an Admin, an HR or an Audit sees the whole organization regardless of team.

The four org roles

Admin

full control. Registers, edits, deactivates and removes people; sets everyone else's org role; creates and re-parents teams; edits the organization's settings; starts and cancels the subscription; and overrides any team lock. The first Admin is whoever created the organization.

HR

takes care of people. Opens the Users page and edits the record — compensation, contract type, work modality, weekly workload, currency, home team and skills. HR can also rewrite the wording of the 1-to-5-star rating scale, the only organization setting open to someone who is not an Admin. What HR does not do: add new people, remove people, change someone's org role or deactivate an account — that stays with the Admin. And there is no vacation, leave or time-off management on the platform; assessing a cycle is the team manager's act, not HR's.

Audit

broad reading, no writing. Reads deliverables, deliverables plans and work plans across the whole organization, with no team restriction. Every write attempt is refused by the server — and the screens do not offer the buttons. But "broad" is not "everything". People records (salaries, contracts, roles) are restricted to Admin and HR. Cost figures do not arrive either: the server only sends the number to the Admin and to whoever manages some team — and the Audit role, on its own, is neither. By the same yardstick, the Reports page does not appear.

User

the default role, and almost everyone's. On its own it gives you nothing beyond your own work: what you reach comes from your team roles.

Where each role lands in the sidebar

Reports follows a different yardstick, because it carries individual assessments: it shows up for the Admin and for whoever is a manager or assistant of some team. An HR who leads no team does not see it.

The four team roles

There are four, not three — the old manual forgot the last one.

Manager

answers for the team. Creates deliverables and deliverables plans, creates work plans for the team's people, signs the supervisor line, approves or rejects edit requests and assesses the cycles. Signing and closing a deliverables plan is theirs alone (or the Admin's).

Assistant

a member with management powers, with two sharp exceptions. An assistant creates deliverables, deliverables plans and work plans, approves and rejects edit requests — but does not sign the supervisor line and does not assess cycles. There is a side effect that catches people out: if "assistant" is your only team role in the entire organization, you cannot sign even your own work plan, which a plain member signs without trouble.

Member

executes. Works on the deliverables, touches the tasks they act on, builds and signs their own work plan, submits the cycle report and can request adjustments and edits. Does not create deliverables and does not assess anyone.

Observer

reading, and nothing beyond it. It was built for a mentor, advisor or outside consultant: sees the team's work plans, never counts as leadership, does not see cost figures and gets no write power over the team's work. The observer role is assigned on the team card, on the Teams page.

What each team role can do

The observer stayed out of the table because it would tick none of its rows: the role grants no writing.

An organization Admin passes every row of this table, in any team. Audit passes none.

Three things that do not fit in the table:

Creating your own work plan does not depend on a team role. Anyone in the organization creates theirs. What requires manager, assistant or Admin is creating someone else's plan.

The supervisor signature checks the role, not the tie. Whoever holds the manager role in some team (or is an Admin) can sign the supervisor line.

Self-managed plans are by design, not a loophole. A manager who is also the plan's participant satisfies both conditions and signs both lines of their own plan — participant and supervisor — with no second manager. In small organizations, where the manager is the one executing, this is what lets the cycle run.

One role per team

In the same team you are either manager, or assistant, or member, or observer — never two. Assigning a new role erases the previous one in that team, with no conflict warning, because there is no conflict to resolve.

Across different teams, roles are independent: you can be manager of Marketing and member of Sales.

Who sees what

Beyond the screens, there are two content rules worth knowing, because they explain why two people see different numbers on the same page.

Cost and salary are stripped on the server. Cost figures show up for the Admin and for whoever is a manager of some team. Assistants, members and observers do not receive them — and it is not the screen hiding them: the server does not send the number. You always see your own salary, on your profile; someone else's, never, unless you are Admin or HR.

Work plans always come restricted. For someone whose org role is "User", the list shows: your own plan, always; the plans of the teams you manage or assist (including sub-teams); and the plans of the teams you observe. Whoever neither leads nor observes any team sees only their own plan. Admin, HR and Audit open any plan in the organization.

Team-level privacy

On the Organization page there is a switch called Team-level privacy, which only the Admin turns on.

Off (default)

deliverables and deliverables plans are visible to the whole organization. It is the mode for whoever wants the entire team to see what the company is doing.

On

someone whose org role is "User" only reads deliverables and deliverables plans of the teams they belong to. Admin, HR and Audit keep seeing everything.

Worth noting that the switch governs deliverables and deliverables plans; work plans are already restricted by default, with or without it, by the rule in the previous section.

A role is not the same as "working on the deliverable"

There is a third axis, and it catches a lot of people out: to touch a deliverable or a task, having the right role is not enough — you need a relationship with that deliverable.

Editing a deliverable

manager or assistant of its team (or of the parent team), or Admin. Being manager of Marketing gives you no power over Sales' deliverables.

Creating a deliverable in a team

the same yardstick, applied to the team you pick.

Creating a task in a deliverable

whoever works on it — the leader of the deliverable's team, someone flagged as a candidate on one of its tasks, or whoever has that deliverable in their own work plan.

Touching a task (progress, status)

whoever acts on it, the manager or assistant of the deliverable's team, or the Admin.

Recording a decision

being on the team is not enough. You have to lead the deliverable's team (or the parent team) or actually work on it.

The whole rule fits in one phrase: whoever works on the deliverable.

Who registers people

Worth repeating, because it is the old manual's most expensive confusion: bringing someone new into the organization is an Admin's act, done by email on the Users page.

A team manager can add to their team people who already exist in the organization, and set their role there. They do not open the people records, do not see salaries and do not invite anyone from outside. If you need someone who is not on the platform yet, the request goes to an Admin.

The last-Admin protection

An organization needs an owner. That is why the server refuses three moves when they would leave the organization with no active Admin:

• demoting the only Admin to another role;
• deactivating the only Admin;
• removing the only Admin.

The message is always the same idea: promote someone else to Admin first. And nobody removes themselves from the people list — removal is always of someone else.