Glossary¶

The words Initiative uses, in plain language. Terms are listed roughly from the biggest idea to the smallest.

Guild¶

A workspace — one separate space for one group of people and all their work. Guilds never see each other's data. You can belong to several and switch between them. See Working with guilds.

Initiative¶

A folder for a big effort inside a guild. It gathers related projects, documents, and tools, and it's only visible to its members. (Yes, the app and the "initiative" feature share a name — context usually makes it clear.) See Working with initiatives.

Default Initiative¶

The starter initiative every new guild comes with, so there's always somewhere to begin. It can be renamed but not deleted.

Project¶

A board for tracking work, made of tasks. It can be viewed as a Table, Kanban board, Calendar, or Timeline. See Projects & tasks.

Task¶

A single to-do on a project. It can have a description, status, priority, dates, assignees, subtasks, and tags.

Subtask¶

A smaller step inside a task, tracked as a checklist item.

Status¶

Where a task sits in your workflow — by default Backlog → To Do → In Progress → Done. Statuses are customizable per project.

Priority¶

How urgent a task is: Low, Medium, High, or Urgent.

Document¶

A page or file inside an initiative — a text document, spreadsheet, whiteboard, smart link, or an uploaded file. Many can be edited by several people at once. See Documents.

Template¶

A saved starting point for a project or document, so you can create new ones already set up the way you like.

Tag¶

A label you attach to tasks, projects, documents, and events to group and find them. See Tags.

Tools¶

The optional extras inside an initiative: the calendar/events, queues, and counters. See Tools.

Queue¶

A tool for tracking whose turn it is — useful for games, rotations, and roster orders.

Counter¶

A tool for tracking a number that changes (a score, health, a budget), bundled into counter groups.

Role (initiative role)¶

A reusable bundle of permissions within an initiative — like "Director" or "Cast" — that decides which tools a member may use. See Initiative roles.

Full access¶

The override held by the built-in Manager role: Managers see everything in their initiative, regardless of per-item sharing. It's unique to Manager — no other role can be given it. See Initiative roles.

Access level (Viewer / Editor / Owner)¶

How much someone can do with a specific project or document: view it, edit it, or own it (edit plus manage who else has access). See Sharing projects & documents.

Member / Admin (guild roles)¶

Within a guild, a member takes part, and an admin also runs the guild (people, invites, settings). Different from platform roles below.

Platform roles (Member / Support / Moderator / Admin / Owner)¶

Server-wide roles that govern the whole installation, not just one guild. The owner is the only role that can change server configuration. See Platform roles.

Break-glass¶

A short-lived, recorded, emergency grant that lets an administrator reach a guild they don't belong to — used instead of any permanent back door. See Platform roles.

Trash¶

Where deleted items go first, so they can be restored within a retention window before being removed for good.

Archive¶

Tucking a finished project or initiative out of the way without deleting it. Archived things can be brought back any time.

Favorites¶

Your personal list of starred projects, for one-click access. Starring is private to you.

Command Center (search)¶

The search box opened with Cmd+K / Ctrl+K that jumps you to anything by name. See Search & shortcuts.

Single sign-on (SSO / OIDC)¶

Signing in with an account you already have (work or school), instead of a separate Initiative password. See Signing in.

BYOK (bring your own key)¶

Supplying your own AI provider key so AI features run on your account. See AI features.

MCP¶

The Model Context Protocol — a safe, optional way to let AI assistants work with your data, using your API key and access rules. See API keys & integrations.

Row-level security (RLS)¶

The database feature that enforces who-can-see-what at the data layer, underpinning Initiative's isolation between groups. See How your data is kept separate.