Core concepts

Limin’s structure

Limin has four main layers:

• A workspace contains your organisation, members and teams.
• A team defines a workflow for a particular area of work.
• An issue represents one unit of work belonging to a team.
• A view presents a selected set of that team’s issues.

Workspace

A workspace is the top-level home for an organisation in Limin. It contains its members, teams, issues, settings and subscription.

The workspace owner manages membership, billing, workspace identity and deletion. Other active members can work with teams, issues and views without access to those owner-only operations.

A workspace can contain multiple teams.

Teams

Teams separate workflows within a workspace. A team might represent a product area, discipline or delivery group.

Each team defines:

• Its name and permanent issue prefix.
• Its members and assignable users.
• Its statuses.
• Its labels.
• Its board and list views.
• Its automatic archive policy.

Every issue belongs to exactly one team.

Workspace membership and team membership are separate. A workspace member can browse a team before joining it, discuss issues within it, but must join the team before being assigned its issues.

Issues

An issue represents one unit of work. Its identifier combines the team prefix with a number, such as ENG-42.

An issue can contain a title, description, status, priority, assignee, labels, comments, resolution notes and relationships with other issues.

Its status determines where it appears in the team’s workflow. Moving it into a status in the Done group records its completion. It can later return to an active status when further work is required.

Changes appear in real time to other people viewing the same workspace.

Views

A view is a particular way of looking at a team’s issues. It combines:

A board or list layout. Filters such as status, priority, assignee, label or recent activity. A name and optional description. Public or private visibility.

Every team starts with 3 system views: All issues, Active issues and Backlog.

Save a new view when a combination of filters is useful repeatedly. Public views are available to other workspace members, while private views are visible only to their owner.

Access and ownership

Workspace ownership controls sensitive organisation-wide operations such as invitations, billing and deletion.

Team membership determines who participates in a team and who can be assigned its work. It does not grant workspace-owner permissions.

See Members, roles and invitations for the complete access model.