Projects and Organizations

Stib separates server-wide administration, organization ownership, and project work. Put a setting at the narrowest scope that should inherit it.

Organizations

An organization groups projects, members, labels, credentials, API keys, and an audit trail. Organization admins manage membership and settings for that scope; global server administrators retain inherited access.

An organization can own several projects. Moving a project transfers its boards, cards, sessions, and related data and requires administration rights on the target organization.

Projects

A project points to a repository directory visible to the server. Its settings cover:

• identity, icon/color, description, and repository path;
• boards and templates;
• project scripts;
• labels and sharing/members;
• project skills and .mcp.json loading;
• default credential and scoped API keys;
• sandbox availability and data retention;
• project history, export, transfer, and deletion.

Changing a repository path affects future Git and agent operations. Verify accessibility and Git detection before saving, especially in Docker where container paths differ from host paths.

Project roles

The current project access model distinguishes:

Role	Typical access
Admin	Full project control, settings, and members
Contributor	Create and run cards without administering the project
Product owner	Create, edit and delete cards in Product backlog columns; read-only everywhere else
Reader	Read-only board and conversation access

A product owner sees the whole board whatever the columns: the role only restricts writing. They cannot run an agent, nor move a card out of the backlog. See Column role.

Global and organization administrators can inherit project administration.

Boards and views

Boards live inside a project and define a workflow. Saved views can cross projects and apply filters, grouping, and layout choices. Use another board for a distinct workflow; use a group for lanes within one workflow; use a saved view when the underlying cards should remain on their existing boards.

Sharing and invitations

Project sharing assigns direct members and roles. Organization invitations manage organization membership. Links and seats can expire or be revoked, and authentication/licence policy may prevent access even when a project role exists.

Next: Settings and Audit & Collaboration.