What is the difference between an organization and a workspace?

An organization is the whole group, a school or a team, with one owner. A workspace is where members work together inside it, such as one class in a school or one team in a company. An organization can have many workspaces.

How do I join a class with a code?

Open the menu under the Nodaro logo at the top of the sidebar and choose Join with a code. Type the eight-character code you were given; the hyphen is optional. The code makes you a member of that one workspace.

How long does an invitation stay valid?

An invitation link is valid for 14 days. Sign in with the email address it was sent to. If it expired, ask for a new one; resending an invitation creates a new link and the old link stops working.

Can a teacher see a student's work?

In a school, work starts private to the student who made it, and administrators, such as teachers, can see and change a member's work by default. The organization can change both settings.

Where does my work go when I switch to a workspace?

Anything you create while a workspace is selected lands in that workspace. Switch back to Personal to work in your own space again.

Workspaces — run a school or a team on Nodaro Cloud with classes, roles and join codes

Organizations let a school or a team work together on Nodaro Cloud. Learn about workspaces, roles, invitations, join codes, sharing and switching workspace.

An organization lets a school or a team work together on Nodaro Cloud. A workspace is where its members do that work: a class in a school, or a team in a company. Each person also keeps a personal space for their own work, unless the organization turns it off. You switch between your personal space and your workspaces from the menu under the Nodaro logo.

Organizations, workspaces and your personal space

Term	What it is
Organization	The group: a school or a team. It has one owner, any number of administrators and members, and settings for every workspace in it.
Workspace	Where members work together. It belongs to one organization and has its own administrators, members and settings.
Personal space	Your own work, outside any organization. It is where you work when Personal is selected.

Organizations are a Nodaro Cloud feature. Self-hosted installs do not include them.

Schools and teams

When you create an organization, you choose its kind. The kind sets the words the app uses and the default settings. You cannot change the kind later.

	School	Team
A workspace is called	Class	Team
Workspace administrator	Teacher	Lead
Workspace member	Student	Member
Where new work starts	Private to whoever made it	Visible to the whole team
Administrators and a member's work	Can see and change it	Can see it
Members and work shared with the workspace	Can see it	Can see and change it
Members can start their own projects	No	Yes

Roles

Role	Scope	What the role can do
Owner	Organization	Everything an administrator can, plus transfer ownership and delete the organization. Each organization has exactly one owner.
Administrator	Organization	Manage the organization's settings, members and workspaces. An administrator is also an administrator of every workspace in the organization.
Member	Organization	Belong to the organization and work in the workspaces they are added to.
Workspace administrator, such as a teacher or a lead	Workspace	Manage the workspace's settings and people.
Workspace member, such as a student	Workspace	Work in the workspace.

An organization administrator can be added to one workspace with a plain member role. That explicit role then applies in that workspace.

Create an organization

Click the Nodaro logo at the top of the sidebar and choose Create organization.

Choose the kind, the name and the address

Choose School or Team, and enter a name. The Address is taken from the name; you can edit it, using lower-case letters, digits and hyphens. A school also needs your confirmation that you have the authority to enrol its students and that you accept the organization terms on its behalf.

Wait for approval

New organizations are reviewed before they open. While you wait, the menu shows the organization as awaiting approval, and nothing else is needed from you.

Create classes or teams

Once the organization is approved, create its workspaces with New Class or New Team, and bring people in.

Bring people in

Invite by email

Use Invite people and paste the email addresses however you have them: separated by commas, semicolons or line breaks. You can send up to 200 addresses at a time.

Choose the Role in the organization: Member or Admin.
Optionally add the people to a class or team at the same time.
Each person gets an email with a link. When an address could not be emailed, you get the link instead: use Copy link and pass it on. The invitation exists either way.

The person who follows the link sees who invited them and to what, and signs in with the invited email address to accept. Invitations are valid for 14 days. Resend creates a new link and the old link stops working. You can also withdraw an invitation that nobody has accepted yet. An organization can send up to 500 invitations a day.

Owners and administrators can always invite. Workspace administrators, such as teachers, can invite new people into their own workspace when the organization allows it.

A join code is eight characters, short enough to read out in a room or write on a board. It makes the person a plain member of one workspace.

A workspace administrator opens the workspace's settings and turns on Allow joining with a code under Join code.
Share the code, for example BCDF-GHJK.
People open the menu under the Nodaro logo, choose Join with a code, type the code and click Join.

The hyphen is optional, and letters that people mishear are accepted, such as the letter O for the digit zero. New code replaces the code, and the old code stops working at once. The organization can limit codes to certain email domains, such as your school's domain. A code never lifts a suspension. After too many wrong attempts, wait a minute and try again.

Switch between workspaces

Click the Nodaro logo at the top of the sidebar. Under Workspaces, the menu lists Personal and, for each organization, the classes or teams you belong to. Choose one to work there.

New work lands where you are. A workflow or project you create while a workspace is selected belongs to that workspace.
Archived workspaces stay in the list. You can still open them and read everything, but nothing new can be added.
Some organizations close the personal space. Then everything a member makes belongs to the organization, and you create work inside a workspace.

A workflow in a workspace is either private to the person who made it or visible to the whole workspace. The organization's settings choose where new work starts.

To change who can reach one workflow, open the Present tab of the editor and its share dialog:

Everyone in this workspace or Only people I share it with sets the workflow's visibility. Only the creator or a workspace administrator can change it.
People with access adds one person by email, as Can view or Can edit. The access starts at once, with no acceptance step.

A few rules keep shared work safe:

People outside the workspace can only view. Someone who is not a member gets view access, even with an edit grant.
Running needs membership. Only active members of the workspace can run its workflows.
Collaborators cannot delete. Only the creator or a workspace administrator can delete a workflow.
Leaving is always allowed. Anyone can remove their own access.

Workflows shared with you outside your workspaces appear on the Shared with me page.

Workspace settings

Settings are layered. A workspace setting wins over the organization's setting, which wins over the default for the organization's kind.

Setting	Choices
What may administrators do with a member's work?	See it, or see and change it
Where does new work start?	Private to whoever made it, or visible to the workspace
What may members do with work shared to a workspace?	See it, or see and change it
Can members start their own projects?	Yes, or work happens inside the places you create
Do members keep a personal space?	Yes, or everything a member makes belongs to the organization
Can workspace administrators invite new people?	Yes, or only organization administrators bring people in
Can collaborators invite further collaborators?	Yes, or sharing stays with the person who owns the work
Who may join with a code	Anyone with the code, or only the email domains you list

Archive, suspend and leave

Archive a workspace when a class ends. Everything in it stays readable, nothing new can be added, and you can move work out of it. An administrator can reopen it.
Suspend a member to stop them acting without removing them. A suspension in the organization applies in every workspace. Reinstate lifts it.
Remove someone from a workspace and they stay in the organization. Remove them from the organization and they leave every workspace in it.
Leave an organization at any time, which also removes you from its workspaces. The owner must transfer ownership to an administrator first.
Delete an organization only after every workspace is archived. Only the owner can delete it.

History

Owners and organization administrators can read the organization's History. It records who was invited, who joined or left, role changes and suspensions. It also records workspaces created or archived, settings changes and join code changes. The history stays readable even while the organization is suspended.

Automations in a workspace

A trigger runs a workflow on behalf of the person who set it up. Every time a schedule, webhook or Telegram trigger fires, Nodaro checks that this person may still run the workflow. When they have lost access, for example because their membership was suspended or the workspace was archived, the automation stops. The workflow's run history then shows one failed run that says why.

Treat a webhook trigger's URL like a password. Anyone who has it can start the workflow.

From code

The REST API, the SDK and the CLI can create organizations, add people, send invitations and manage join codes. They also choose the workspace a request acts in. Assistants connected through MCP can list your workspaces and select one. See the Workspaces API.

Workspaces