Workspaces
A workspace is where your team works in Skyelight. It holds your members, the projects you collect feedback on, and the surfaces and pins inside them. Everything you do happens inside a workspace, and membership in that workspace decides what you can see.
One level up is your organization: the account that owns your workspaces and will hold billing once paid plans launch. During free beta there is nothing to pay. Most teams have a single organization with a single workspace.
Members and roles
People join a workspace by invitation. Each member has a role that controls what they can do:
| Role | Pin & reply | Resolve threads | Invite members | Manage settings |
|---|---|---|---|---|
| Owner | Yes | Any thread | Yes | Yes |
| Admin | Yes | Any thread | Yes | Yes |
| Collaborator | Yes | Their own | Yes | No |
Invite teammates from the workspace Settings → Members. Invitations are sent by email, and people pick up the role you assign when they accept.
Everyone who leaves feedback needs a (free) Skyelight account, so each comment is attributed to a real person. Accounts for people who only contribute feedback — your clients, stakeholders, and other collaborators — are free forever, during beta and after it ends.
What a workspace scopes
Membership is the boundary for access. A member of the “Acme” workspace sees Acme’s projects and pins, and nothing from any other workspace. When a pin is created, replied to, resolved, or assigned, only members of that workspace are notified.
Billing and organizations
Skyelight is in free and open beta, so there is nothing to pay today and no card to add. When paid plans arrive (we will notify everyone well beforehand), billing will belong to the organization, not the individual workspace, and your plan will apply across every workspace the organization owns.
Pricing will be based on the people who manage workspaces and projects. People who only leave feedback are always free, so you can bring in as many clients and stakeholders as you like. You will manage members and billing for the organization from Settings in the dashboard.
When to use more than one
Most teams need a single workspace. Reach for a second one when you have a genuinely separate group of people and projects, for example, an agency keeping each client fully isolated. If you only want to separate sites or areas of a product, use projects instead.