Skip to content
HamstikHamstik Docs

Teams

Teams

Hamstik has two distinct kinds of teams, and they do different things:

  • Access Teams are organization-wide groups of members. They are prepared for future permissions. In this release an Access Team grants nothing. Use Members and per-Project access for permissions today.
  • Delivery Teams are project-wide groups used for planning, ownership, and reporting. A Delivery Team never grants access. People must already have effective access to the Project before they can join one.

The two types are independent: the same name can exist in both, and the same name can exist in two different Projects.

Managing Access Teams

Organization owners and administrators manage Access Teams in Organization settings → Access Teams. Members with organization access can view team names and membership; guests cannot.

  • Create a team with a name and an optional description.
  • Add active organization members one at a time. Adding someone who is already a member has no effect, and removing someone who is not a member is harmless.
  • Rename or redescribe a team at any time. Renaming keeps the same team and membership.
  • Delete a team only while no authorization reference points at it. Deleting removes the membership list, but the append-only audit history keeps the team name and member identities.

Managing Delivery Teams

Effective Project admins (including organization owners and administrators) manage Delivery Teams in Project settings → Delivery Teams. Any current Project reader can view team names and membership.

  • Only active organization members with effective access to the Project — an explicit membership or the Project’s inherited default access — can be added. A member with no access cannot join.
  • Multiple team memberships are allowed.
  • Archive a team to keep it readable and keep its reporting identity while stopping new members and new selections. Restore reintroduces it to selection; it does not restore members who were removed, and anyone who lost Project access while it was archived is pruned on restore.
  • Permanently delete a team only while it is empty and no business data references it. If it still has members or references, archive it instead.

Names and descriptions

Names are trimmed, normalized to Unicode NFC, and limited to 1–100 characters without control characters. Uniqueness compares a full case-folded key, so Straße and STRASSE (and Unicode equivalents such as fin and fin) are the same name:

  • Access Team names are unique within an Organization.
  • Delivery Team names are unique within a Project, including archived names.
  • The same name in another Project or in the other team type is allowed.

Descriptions are optional plain text up to 1,000 characters.

Access changes

Membership follows access; it never creates it.

  • Removing someone from the organization removes their Access Team and Delivery Team memberships in the same transaction.
  • Losing access to a Project removes that person’s Delivery Team memberships, including when an administrator lowers the Project’s default access policy or an Organization role change removes implicit Project admin.
  • Restoring access, rejoining the organization, or restoring an archived team does not silently bring membership back. A manager must add the person again.
  • Audit records are preserved throughout.

Public API

Organizations and Projects expose team lifecycle and paginated membership through Hamstik Public API v1. See the API resources reference for the exact routes, scopes, and lifecycle rules.