Organizations
An Organization is Hamstik’s shared workspace boundary. Projects, Work Items, Boards, Sprints, labels, and organization-level settings are scoped to the Organization that owns them.
Membership and roles
People can belong to multiple Organizations. Each membership has an Organization role:
| Role | Typical responsibility |
|---|---|
| Owner | Full Organization administration and ownership responsibilities. |
| Administrator | Manage Organization settings and members within the available administrative controls. |
| Member | Work in the Organization’s Projects according to the access granted by the workspace. |
The exact action allowed by a role is enforced server-side. A URL, browser state, or API token cannot substitute for current membership.
Manage members
From Organization settings → Members, owners and administrators manage the organization’s people directly. The permission matrix:
| Action | Owner | Administrator | Member |
|---|---|---|---|
| View the member roster | Yes | Yes | No |
| Change another member’s role | Yes (admins and members) | Yes (members only) | No |
| Remove another member | Yes (admins and members) | Yes (members only) | No |
| Leave the Organization | Yes | Yes | Yes |
| Transfer ownership | Yes | No | No |
Two rules apply on top of the matrix:
- Rank. Nobody can change or remove someone at or above their own role, and you cannot change your own role. An administrator acts on members; an owner also acts on administrators.
- Owners are special. An owner’s role changes only through ownership transfer, and the organization always keeps at least one owner. The last owner cannot leave, and owners cannot be removed — transfer ownership first.
Removing a member takes effect immediately: the person loses access to the Organization’s Projects, Work Items, and settings on their very next action, even through a stale browser session or an existing API token. Their comments and work history stay intact. Leaving works the same way; the last owner must transfer ownership before leaving.
Membership changes are recorded in the audit trail with the actor, target, Organization, time, and outcome.
Organizations with Enterprise coverage can manage members through SCIM 2.0 user provisioning from Organization settings → User provisioning: your identity provider creates pending invitations and deactivates members, while each provisioned person still accepts while signed in before access begins. See the SCIM provisioning guide for the supported subset and credential lifecycle. SAML single sign-on with optional or enforced modes is configured from Organization settings → Security & sign-in; see SAML single sign-on.
Organization settings
Organization settings include membership and invitation management, label discovery across Projects, import/export controls, installed Applications, and plan-related information where available. The Apps area keeps Installed and Discover views. Premium Applications show access, independent enablement, retained-data, and renewal state. Owners review Premium billing from the Billing section; administrators can enable or disable an entitled App without receiving billing authority.
Allow public Projects
Organization settings → General → Allow public Projects is the organization-wide opt-in for public sharing. When it is off — the default — no Project in the organization is ever guest-visible, regardless of its own setting. Turning it off acts as an immediate kill switch and revokes all guest reads on the next request. Turning it on does not publish anything by itself; each Project must then be published explicitly by its Project or Organization administrators.
Organization image
An Organization can have one image (logo). Owners and administrators can upload, replace, or remove it from Organization settings → General information. PNG, JPEG, and WebP files are accepted up to 5 MiB; Hamstik keeps the uploaded original and generates one optimized 96-pixel WebP for the interface, so the switcher, Organization header, dashboard, and Organization lists stay fast.
Organization images are private to Organization members. The image is served through an authenticated Hamstik route under the same access rules as the rest of the Organization — it is never a public or directly linkable object-store URL. When no image exists, the standard Organization icon is shown.
Attributes
Attributes add an Organization-governed vocabulary for classifying Work Items across Projects — for example a Customer, Product Area, or Regulatory Classification. They are optional metadata: they never change how work moves, and first-class Hamstik properties and Project Labels stay separate.
Each Attribute has:
- a permanent key — lowercase letters, digits, and underscores, unique inside the Organization, including retired records. A rename changes the display name only; assignments, saved queries, and API references keep working through the same identity.
- a type, fixed at creation: Single select, Multi select, or True / false. Select definitions carry options with their own permanent keys, editable labels, and an administrator-controlled display order. True/false Attributes keep unset distinct from a chosen false.
- a lifecycle: active Attributes accept assignments wherever a Project opted in; disabling is reversible and stops new assignments while preserving existing values, opt-ins, and queries; retirement is permanent — records stay readable, queryable, and exportable, no new assignments are accepted, and keys can never be reused.
Owners and administrators manage the vocabulary in Organization settings → Attributes: create, rename, disable, re-enable, retire, and administer allowed values. Members can discover the vocabulary they may assign but cannot administer it. Every administrative change — create, rename, option add/rename/reorder/retire, disable/re-enable, retire, and Project opt-in/out — is recorded with the actor, Organization, stable target, timestamp, and before/after state.
In Show options, use Rename to edit an option label while retaining its permanent key. Use Retire to stop future selection without erasing existing assignments. Retired options remain listed with a Retired badge. Retirement is permanent; re-enabling an Attribute does not revive retired options.
An Organization can hold up to 25 definitions, each select definition up to 50 options, and a multi-select assignment up to 10 distinct selections. Disabled and retired definitions/options still count toward these limits. Definition keys are 2–40 characters; option keys are 1–40. Both start with a letter. Names and option labels are limited to 100 characters; native property names such as status and labels are reserved keys.
Changes use the revision you read. If another administrator changes the vocabulary first, Hamstik reloads its current state so you can review and retry. An unsaved option’s key and label stay in the form after this conflict.
Organizations and Enterprise
An Enterprise is a commercial agreement above Organizations. One Enterprise can cover unlimited Organizations — for example regional, regulatory, or contractually separated workspaces — with consolidated usage-based billing, a single $1,000 annual minimum, and priority business-hours support.
Enterprise membership is a billing relationship only. It never grants an Enterprise administrator access to another Organization’s settings, Projects, Work Items, or attachments. Each Organization keeps its own members, roles, and workspace boundary.
Free and Pro Organizations support up to 50 users; Enterprise Organizations have no fixed user limit. See Plans & limits.
Manage an Enterprise
Enterprise Owners open Account, choose the Enterprise administration entry, and then use the Enterprise sections for Overview, Organizations, Usage & Billing, and Administrators. The Overview shows the current status, associated Organization count, active-user and storage estimates, the annual minimum, and the current Enterprise Owners.
From Organizations, an Enterprise Owner can create a new Organization or add an existing Organization. Creating one follows the normal Organization creation rules, including making the creator an Organization Owner. Adding an existing Organization requires the acting user to be both an Enterprise Owner and an Owner of that Organization. The Enterprise Owner can see billing-safe metadata such as membership counts, active users, and storage; this does not expose Projects, Work Items, attachments, settings, or other Organization content. Premium Applications included through Enterprise are independent per Organization and are not automatically enabled.
An Organization with an active paid subscription is not eligible for direct association because that could create overlapping billing. End or resolve its subscription through the Organization’s normal billing settings first, then add it to the Enterprise; the Enterprise workflow never creates a duplicate subscription.
Removing an Organization requires confirmation and returns it to the normal Free/Pro billing path. It is blocked while the Organization has more than 50 members. Direct reassignment between Enterprises is not supported: use the safe remove-and-add workflow, subject to the same authority, active-term, and membership checks. Historical usage remains with the Enterprise term that owned it.
Usage & Billing presents the $1,000 annual minimum, the current annual term, usage-to-date, estimated current charge, and the Organization breakdown. Enterprise active users are deduplicated across associated Organizations. From Administrators, Owners can add or remove Enterprise Owners; Hamstik always requires at least one Owner.
Enterprise administration is separate from Organization administration. An Enterprise Owner does not become an Organization member or gain access to its work unless they independently hold the relevant Organization role.
Invitations
An invitation is associated with the Organization and the role proposed by the inviter. The invitee’s access begins only after the invitation is accepted and the membership is established.