Set up your company workspace

Set up your company structure in Node Cluster, create Spaces, invite a pilot team and verify access through a practical first workflow.

Set up one shared organization for the company work your team will manage together. Start with a small working group and one real process, then extend the structure once people can find and update their work.

Who this is for: the workspace owner or an administrator. Allow time to test with a colleague who has a normal Member account.

1. Establish the organization

If your company does not already have a workspace, open the organization setup flow at /org/new. Choose Let’s go, enter the Workspace name, and submit the form to create it. If the company already has a workspace, ask for an invitation instead of creating a second one. Confirm the selected organization before inviting people or adding work.

Choose a company name people recognize. A customer engagement or campaign normally belongs in a project within this organization; it does not need its own organization.

2. Create the departments you need first

In Spaces, create a Space for each participating department—for example Customer Success, Marketing, and Company Operations. Owners and administrators create these company Spaces. Start with two or three that have real work ready to move in.

Use a folder when it makes a larger list easier to navigate. Customer Success might have an Active onboardings folder containing one project per customer. A small department can keep projects directly inside its Space.

3. Invite the pilot group

Open Team → Invite. Enter each colleague’s email, choose their organization role, and select the areas they need. Most people doing everyday work need Member and Spaces. Give Operations access to people who administer resources or connected services. Reserve Admin for people who need broad administrative authority.

An invitation and its selected areas are only the start. After the colleague joins, open their member record to configure department access and project-creation authority.

4. Configure access and creation separately

Give the colleague access to the departmental work they should use. Then open Project creation governance and assign their primary department. For Members, that department is their baseline destination for creating projects. Add an explicit exception only if they also need to create projects in another department.

These are two separate decisions: which work may this person use, and where may this person create new projects. Setting the primary department does not share the department’s existing projects.

5. Prepare the first working project

Create a real project, such as Customer onboarding — Northstar, in the appropriate Space. Add a short purpose, a few actionable tasks, owners, dates, and the supporting notes or files. Select BAU for an ongoing workstream or Project for a finite delivery. Review task assignment policy and sharing before asking the team to start.

6. Verify the experience together

Ask a Member to open Spaces, find the project, open All Tasks, and make an allowed update. Check that they can find the intended department and that unrelated restricted work is unavailable. Ask them to create a project only where that is part of their role.

Finish setup when the team can carry out a real handoff: one person records work, another finds it, and the responsible person updates it. Add integrations and reporting after identifying the operational need they will serve.