A Space is an Organization-owned boundary for a continuing area of work. Every task belongs to exactly one Space, and the Space supplies the task identifier, available task types, workflows, Space labels, Views, Sprints, and Automations used for that work.Use separate Spaces when work needs a different access boundary, set of task types, or operating cadence. Use Projects, labels, or Views when you only need to group or display work differently.Organization and Space ownership#
An Organization is the top-level isolation boundary in Sharkly. Spaces, tasks, Projects, statuses, custom fields, Views, People, Agents, and other records cannot be shared across Organizations.A task belongs to one Space and uses a task type owned by that Space.
A View belongs to one Space.
A Sprint belongs to one Space.
An Automation belongs to one Space.
A Project belongs to the Organization and is associated with one or more Spaces.
Task statuses and custom fields are reusable Organization definitions. Space task types select the statuses and custom fields they use.
Create a Space#
When you create a Space, define:Name: the name shown in navigation and settings.
Identifier: a unique 2–7 character code used in task IDs, such as ENG-123.
Icon and color: visual identifiers used throughout the app.
Access: Public to organization or Private.
Work setup: recommended task types, statuses, and labels, or settings copied from another Space.
Public and Private Spaces#
Space access is separate from Organization role.Public to organization#
Organization Owners, Admins, and Members can find and join a public Space. Joining adds the person as a Space member.Guests do not automatically discover or join public Spaces. They can access only Spaces to which they have been added.Private#
A Private Space's tasks and working content are available only to its Space members. Organization Owners and Admins can still see the Space's metadata and manage non-roster configuration, but without Space membership they cannot access task content or the Space members roster.Add People explicitly when they need to work in a Private Space.Space membership and roles#
Every Space member has one Space role:Administrator: manages Space settings, configuration, and membership.
Member: creates and updates work in the Space.
Viewer: in a Private Space, cannot create or edit tasks but can still comment and add attachments. In a Public Space, the Viewer role does not add the same task-edit restriction.
Task types and workflows#
Task types are owned by the Space. Each type has one bounded Workflow containing an ordered set of reusable Organization statuses and one default status.This lets different Spaces model different kinds of work without duplicating the Organization status catalog.Labels#
Tasks in a Space can use Organization labels and labels owned by that Space. Space labels are useful for local modules, areas, or classifications that do not apply everywhere.Sprints#
Sprints can be enabled per Space. A Space can use an automatic cadence or manually create, start, and complete Sprints.Views and Automations#
Views and Automations are also Space-scoped. A View saves a way to inspect tasks in its Space. An Automation stores its Space context, instructions, assignee, triggers, and run history.Retire, restore, or delete a Space#
Retire a Space when its work should remain available but no longer be edited. A retired Space is read-only and can be restored later. During retirement, Sharkly asks how to handle unfinished tasks, such as canceling them or moving them to another Space.Deleting a Space is permanent and has stricter checks. Use retirement when historical tasks, Projects, Views, or settings still need to be retained.Choose a useful Space boundary#
Create a new Space when at least one of these is true:The People who need access are materially different.
The task types and Workflows are different.
The work needs its own Sprints, Views, labels, or Automations.
The work is a stable operating area rather than a short-lived classification.
Modified at 2026-08-04 04:02:55
