Project settings

Every settings tab of a project, what it configures and who can change it; the Trash; archiving and deleting a project; the limits you can meet.

Last updated 2026-10-10

The gear next to the project’s name opens its Settings. Every member sees every tab; changing anything takes Admin, and a few buttons take the Owner. Git, Webhooks, Embedding and the runner-pool grants show their contents to Admins only, and Export to the Owner only. On an archived project the controls are disabled and a banner says why.

The tabs, in order: General, Members, Roles, Workflow, Agents, Packs, Types, Custom fields, Components, Saved filters, and under Integrations: Git, Webhooks, Embedding. A project without the tasks module — a Library — has no Workflow, Custom fields, Components, Saved filters or Git.

General

• Name and Description are yours to change; the Key never changes, so task keys stay what they were. Languages sets which content languages the project carries; disabling one asks for confirmation and spells out what it means. Timezone governs due dates and the day boundary of the sprint burndown.
• Agent writes holds two switches. Content writes via MCP require approval — off by default — makes an assistant’s edits to existing content wait as drafts; a project agent’s always do. Agent tasks start in Triage — on by default — sends a task an agent files without a status to the triage status, when the workflow has one. See Review what your AI proposes.
• Translation names the Translator agent that translation requests go to; Conversion names the Converter agent that converts scanned or opaque files — see Files and spreadsheets.
• Export — the Owner only — starts a whole-project export, built in the background; only the person who started it can download it, for up to seven days (the next export replaces it), through a link that lasts ten minutes. The section lists every export of the project, members’ audit-log exports included; any member exports the audit log from the Audit page.
• Danger zone — the Owner only. Archive makes the project read-only everywhere, MCP and agents included, cancels queued agent jobs and hides it from the default lists and search; Unarchive brings it back — the cancelled jobs do not return, pending invitations are revoked for good — and counts it against the Owner’s active projects again. Delete project is offered once the project is archived: type its name to confirm, and it leaves everyone’s view at once. For seven days it can still be restored by the operator, as an archived project — the dialog shows the contact; on app.rindo.io, write to support@rindo.io — after which it is purged with its files and its exports.

Members

Covered in Invite your team: Add member by username or by e-mail, the Permission of each member, Roles… to assign work Roles, Transfer ownership… on a member’s row, Leave project on your own, Remove on anyone but the Owner, and the lists of Pending invitations (resend or revoke) and, for the Owner, Pending ownership offers.

Roles

Work Roles — BA, QA, reviewer — each with a key, a name, a description that agents match on, and an Instructions page written for its holders. Members get Roles from Roles… on their row in Members; agents get them in the agent’s edit drawer; this tab counts the holders. Roles grant no permission. See Roles and guidance.

Workflow

• Statuses — add, rename and order them; the order is the board’s column order. Each status has a Category — Triage, To do, In progress, Done — which gives it its colour and its meaning to every count. Set as default marks where a new task lands; only a triage or to-do status can be the default. Deleting a status that holds tasks asks where to move them first.
• Triage — the switch that gives the project a triage status. Turning it off deletes every triage status after moving their tasks; turning it on adds New at the top of the workflow.
• Transitions — a from-and-to grid, every box ticked for a new status; untick to restrict. The board and every agent refuse the same moves.
• Diagram — a read-only picture of the workflow, with Copy as Mermaid.

Agents

Register agent creates a project agent by handle; its runner token is shown once, Revoke token ends it, and Rotate runner token is offered while the agent has no pool. Edit handle opens the agent’s drawer — handle, instructions page, model hint, runtime, pool, Roles — and Edit scope… its capabilities; Deactivate stops it and cancels its queued jobs; an agent with no history at all can be deleted, otherwise deactivate it. Runner pools is where an Admin grants a pool — their own, or the instance’s — to the project and revokes it; revoking cancels the project’s running jobs on that pool. Runner setup and Job history sit on the same tab, and the history is readable by everyone. See Run your own runner.

Packs

A pack is a published snapshot of a project’s guidance, pages and skills that another project can bind and inherit. Publish pack and Yank publish this project’s; Bind pack…, Advance… and Unbind manage the packs bound to it, and Opt out leaves one the operator bound for every project. On app.rindo.io only the libraries the operator has exposed can be bound.

Types, fields, components, filters

• Types — the work item types and document types, each with a name and an icon; one is the default; deleting a type that is in use first asks which type its items move to. A document type can carry a default template. Types are metadata, never folders.
• Custom fields — per-project fields on tasks, documents and test cases alike: text, number, date, select, checkbox, URL or user. A field’s type is fixed at creation; a field that holds values is deactivated rather than deleted.
• Components — areas of the product to group tasks by, with a name and a description; deleting one keeps the tasks and their history.
• Saved filters — the filters saved from the task list with Save current view…: yours, and the shared ones only an Admin creates or changes.

Integrations

• Git — the project’s GitHub and GitLab connections: GitHub and GitLab.
• Webhooks — the receiver endpoint of each connected repository and the Event log of what arrived, newest first. It is the inbound side only; Rindo does not send webhooks.
• Embedding — the semantic-search configuration. On app.rindo.io every project uses the instance’s; a per-project override is refused. When a monthly embedding limit is reached, semantic indexing pauses and keyword search carries on.

The Trash

Deleted tasks, documents and test cases go to the project’s Trash at /p/<key>/trash — an Admin’s page, with no link in the navigation. The banner says how many days items are kept before they are purged; Restore brings one back, a document with its sub-pages, and a page whose parent is still in the Trash needs the parent restored first. There is no emptying the Trash early. A deleted project is not here: it is restored by the operator.

The limits you can meet

When an action would pass one of the limits of the project owner’s plan, Rindo refuses it with a message that names the limit and, where there is one, the way out: archive a project (archived ones do not count toward active projects), deactivate an agent, revoke a token, wait a day for the upload allowance. The plans themselves are on the pricing page.