Spaces and Pages

Working with Spaces

Working with Spaces

A space is a container for pages inside a Nexus. Create one per team, product, or subject.

Create a space

Open a Nexus, then use any of these:

• Sidebar: the Spaces section header has a + button, tooltip New space.
• Nexus page: the Create Space card at the end of the spaces grid. Type a name, press Enter or click Create.
• Empty Nexus: the sidebar shows Create your first space.

There is no keyboard shortcut for this. ⌘ ⇧ N is reserved but not wired to anything.

The sidebar route opens the Create new space dialog with a Space name field and a subtitle showing which Nexus it lands in. Click Create and you land in the new space. The slug is generated from the name and is not editable afterwards.

The space page

A space opens at /space/{id} and shows a directory of its contents, not an editor. The header carries the icon, name, the primer’s one-line brief, a Primer button, labels, an Everyone indicator (what a member of the Nexus gets here without a grant: No access, View or Edit; if your own access here is held at View below that, it reads You: View instead), an Access button, and the watch controls. Two grouping modes sit beside them, Type (folders first, then pages) and Label. Your choice is remembered per space.

In the Type grouping, anything that holds contents of its own, a folder or a page, carries an arrow ahead of its title. Click it to open the tree of what is inside without leaving the space, and click it again to close it. The rows inside carry their own arrow, one level further. The Label grouping is a flat list and has no arrows.

The right rail holds create buttons: New page, New folder, and one per plugin document type installed. If you can only view the space there is no rail, and nothing in the space header, the sidebar or the empty directory offers to create, rename or move anything.

Space settings

Click the gear icon in the space header, tooltip Space settings. The menu shows only what your access allows: Edit space, Change cover and Child indexes need edit access, Move to nexus and Move to Trash need full access, and Duplicate space needs you to be a member or admin of the Nexus (not a guest). The menu:

Administrators get a second route in: on the Nexus page, each space card’s right-click menu offers the same Edit dialog, and Access opens the same panel.

Name and icon

The Edit space dialog holds two fields:

Click Save changes to commit.

The line that shows under the space name is the primer’s Brief, edited behind the Primer button beside the name. See Primers.

Who can reach a space

The Access panel (the header button, or Space settings > Access) lists everybody who reaches the space, one row each, with the level they hold and an (i) that says why:

Anybody who can see the space can open the panel and read it. Changing anything on it needs full access on the space or a Nexus administrator role; below that the rows carry no controls. To add a person or a group, use the box at the foot: pick them, pick a level, optionally a date the access ends, and press Add. A person who is not in the Nexus can still be added and reaches this space and nothing else.

Move a space to another Nexus

Choose Move to nexus. The Move Space modal lists every other Nexus you administer, other than your own personal one. Pick a destination, then click Move Space. You land back at the Nexus list.

The space takes everything in it along: its pages, their files and images, the space’s own templates, a Confluence sync set up for it, and any requirements collections. The labels on its pages belong to the old Nexus and stay there, and so do the old Nexus’s audit entries about the space. A connection the space uses (a Git Docs page, a Kanban board, a Confluence sync) keeps working only if the new Nexus may use that connection.

A requirements collection keeps using the old Nexus’s systems and external items for as long as the old Nexus exists, so its allocations and links still show after the move. If the old Nexus is deleted later, the collection and its requirements stay, and those allocations and links go with the old Nexus.

If there is no other Nexus you administer, the modal says No other nexus available. An administrator of the Nexus you want can make you one of its administrators.

Make a space a folder in another space

A space that should have been a folder can become one. Choose Make it a folder… in the Space settings menu, then pick the space it goes into. Both spaces must be in the same Nexus, and you need full access on both. The folder lands at the top of the space you pick.

The dialog says what will happen before anything does:

• A folder with the space’s name, icon and cover holds every page that was in the space, including any in the Trash. Page addresses do not change.
• What changes for people, by name, both ways: the folder takes the access of the space it lands in, so people who could open only the old space lose it, and people who can open the destination can now read everything that was in the old space. Sealed pages keep their seals.
• The old space’s access list is removed. Every share link on its pages stops working, and cannot be brought back. A Confluence sync set up for the space is removed.
• The space’s labels go on the folder, its templates move to the destination, people watching the space watch the folder instead, and its primer becomes the folder’s.

A space with pending access requests cannot become a folder until they are decided or withdrawn, and neither can a space whose chat channel holds messages.

The space itself is deleted and does not go to the Trash. To undo, open the folder and choose Make it a space…. The space’s old address leads to the folder.

Make a space a Nexus of its own

A space that has grown into a whole organisation’s worth of content can leave its Nexus and become the first space of a new one. Choose Make it a nexus… in the Space settings menu. You need to be an administrator of the Nexus the space is in.

The dialog says what will happen before anything does:

• A new Nexus named for the space holds it with every page. No address changes, and share links, watches and links between pages keep working.
• Who is in the new Nexus, by name: everyone named on the space joins it, Full access as an admin, Edit as a member, View as a guest. You join as an admin. A group cannot leave its Nexus, so each member of a group named on the space joins in person, with the group’s access.
• Only access that does not expire makes someone a member. A person whose access to the space ends on a date keeps that access, shown as Granted only with the date, and loses it on that date. A person who also holds lasting access joins with the lasting access and keeps only that, so the higher access that would have ended is lost now; the dialog lists them.
• What changes for people, by name: an administrator of the old Nexus who is not named on the space loses it, and so does a member who reached it only through the Everyone level.
• Who can newly open, and who can no longer open, the space’s sealed pages. An administrator of a Nexus can open a sealed page without being granted it, so everyone who becomes an administrator of the new Nexus, or stops being one, is named with the number of sealed pages that changes for them.
• The labels on the space and its pages are copied into the new Nexus, and the space’s templates, files and Confluence sync go with it.
• The space’s history stays in the audit log of the old Nexus, where it was written.

A space with pending access requests cannot become a Nexus until they are decided or withdrawn.

Delete a space

Choose Move to Trash in the Space settings menu. The confirmation reads:

“Space name” will be moved to Trash. Restoring it from Trash brings back every page in it.

Press Move to Trash to delete. Deleting requires full access on the space. The space and its contents vanish from the Nexus immediately, and the space lands in Trash, under the Spaces tab, where you can restore it until someone permanently deletes it. See Trash and Restore.

On the Nexus page, Move to Trash on a space card’s right-click menu asks the same question, and so does the Delete button at the bottom left of the Edit space dialog opened from that menu. The Edit space dialog opened from the space header has no Delete button.