Spaces

Use Spaces to choose who can access a group of prototypes. Within a Space, folders help organize the work without changing its audience.

The three kinds

Space	Who can open its content
Organization	Everyone in your organization. New work goes here by default.
Personal	Only you; other members and org admins can’t open its content.
Shared	Members you add, plus org admins for oversight. You can also open it for organization-wide reading. Requires Team or higher.

Organization and Personal Spaces are created automatically and can’t be renamed or deleted. You create and manage Shared Spaces.

Where you land

Signing in takes you to the Spaces picker, so you always start by choosing a Space. Opening the dashboard again later, from a bookmark or a restored tab, takes you back to where you left off in that organization: the Space, folder, or prototype you last had open, or the Spaces picker if that is where you ended. Artor remembers this per organization and per account in your browser, so another person signing in on the same computer starts from the picker, not from your last folder.

If that place no longer exists or you can no longer open it, the next open starts from the Spaces picker. Choosing Organization in the Space switcher, or clicking the Artor logo, always takes you where the link says. It never bounces you back.

Opening a prototype link

A link to a prototype, from a comment email or pasted by a teammate, opens that prototype even if you’re working in a different organization right now. If you belong to more than one organization, Artor switches you to the one that holds the prototype. This also works when you have no organization selected, or when the one you had open was deleted or you were removed from it.

If the prototype can’t be opened, the page says Prototype not found: it may have been deleted, it may be in a Space you can’t access, or you may not be a member of its organization. If it fails to load, the page says Could not load this prototype; reload to try again. Both pages have a Go to Spaces button to get you back.

Your current organization is shared by every tab in your browser. If two tabs have prototypes from different organizations open, switching between them switches the organization too, and the tab you’re looking at wins.

Create a shared Space

Open Spaces, create a Shared Space, and give it a name. Add teammates from its member controls. Choose a Space when setting up a prototype with artor init, or move existing work into it from the dashboard.

Moving work between Spaces changes who can access it. Preview links stay the same. Existing public links can still provide access to the prototype; review those separately.

Members and roles

Space admin: can rename the Space, manage members, change organization-wide reading, and delete it. A Space admin manages that one Space only.
Space member: can work with its content, subject to their seat.
Org admin: can do everything a Space admin can, in every Shared Space, without being a member of it.

A Shared Space must keep at least one admin. Appoint a replacement before removing or demoting the last one.

Managing a Space is separate from working in it. An org admin who hasn’t joined a Shared Space can rename it, manage its members, and delete it, but can only view and comment on its prototypes. To publish, move, or edit content there, they add themselves as a member first. Every one of these actions appears in the audit log with the admin’s name. Org admins can’t open or manage someone else’s Personal Space.

Bringing people into a Space

In a Shared Space you administer (or any Shared Space, if you’re an org admin), open the projects toolbar’s ··· → Invite members menu:

Org. members: find existing teammates by name or email, then add them as members or Space admins.
Invite to Org: send an email invitation that also adds the recipient to this Space when accepted.

Personal Spaces can’t have other members.

Any member can invite people into the organization, but only org admins can choose a publisher seat or admin role. Other invitations join as reviewers. See Seats.

If the Space is deleted, or the inviter stops being its admin (or an org admin) before an invitation is accepted, the person can still join the organization but won’t be added to the Space. Ask a current Space admin or an org admin to add them. Resending doesn’t change the invitation’s Space.

Letting the whole organization read a Space

Turn on Let the whole organization read in the Space’s manage panel. A Space admin or org admin can change this setting. The Space then shows Open to org.

Members outside its member list can open prototypes and leave feedback. They can’t publish, move or delete work, manage folders, change access, create public links, or edit its configuration and sample data. Space members retain the permissions their seat allows.

This includes people who join the organization later. To limit access to named people, leave organization-wide reading off and add them individually.

Turning it off removes that access on the next request. Existing comments remain credited to their authors. The Organization Space is always open to the whole organization.

Reviewer seats are always read-only

A reviewer can view and comment, but can’t publish or edit prototype content, even in their own Personal Space. Being an admin doesn’t remove those seat restrictions.

Reviewers who are members of a Space can still share publicly. They can also clear or delete a folder with its contents in their own Personal Space. See Seats for the full list.

Getting the code out is seat-based

Downloading prototype source with artor pull, or its local configuration with artor env pull, requires a publisher seat and access to that prototype. This also applies to publishers reading an Open to org Space. Organization-wide local configuration can be pulled by any organization member; see Environment variables.

Closed Spaces are visible by name

A Shared Space you can’t access still appears on the Spaces page as a locked card with its name and No access. Its members, folders, prototypes, comments, and counts aren’t shown. Don’t put confidential information in a Shared Space’s name.

These locked cards don’t appear in the Space switcher, sidebar, or CLI. Other people’s Personal Spaces aren’t listed for ordinary members; org admins can see their existence and usage for oversight, but can’t open their content.

Deleting a Space

When deleting a Shared Space, choose where to move its prototypes. Artor moves them, including trashed prototypes, before deleting the Space. Prototypes aren’t destroyed, but the old folder structure isn’t preserved. Review who can access the destination before moving.

From the CLI

See Installing the CLI if you haven’t set it up.


artor space list
artor space create "Research"
artor space members "Research"
artor space members "Research" add person@example.com  # Space or org admin only
artor space read "Research" on                         # Space or org admin only
artor space rename "Research" "Design research"         # Space or org admin only
artor space rm "Design research" --move-to <folder>      # Space or org admin only

Use an exact Space name or identifier for permission changes and deletion. Ambiguous names won’t be acted on. See the CLI reference for options.

What Spaces don’t cover

Public links: anyone holding an active public link can open its target, even without Space membership.
A record of every viewer: opening a version isn’t recorded against each person. Comments record feedback, not everyone who looked.
Separate plan allowances: usage across all Spaces counts toward the same organization plan.