Settings
Settings in the top bar, or /p/{projectId}/settings. A rail of pages, each with its own
address, so a document can link to one. The owner and admins see two more than a member does.
| Page | What lives there |
|---|---|
Properties …/settings/properties |
Every field on a task. Create, rename, recolour, reorder, delete. |
Types …/settings/types |
The select whose options are the task types, and which properties each type shows. |
Card view …/settings/card |
What a card on the board carries, where each row sits and how it reads. |
Views …/settings/views |
Rename, regroup, reorder and delete views, and name the main one. |
People …/settings/people |
Members and their roles, agents, and the tokens that connect them. |
Webhooks …/settings/webhooks |
A call out of the board when something changes. Owner and admins. |
Import …/settings/import |
Bring a board in from a Trello export. Owner and admins. |
Project …/settings/project |
The project name, the task-key prefix, the time zone, what done means, the export (owner and admins), and deleting the project. |
The rail counts what is on each page, and its foot names the version you are running.
Taking the project out
Section titled “Taking the project out”An owner or an admin sees an Export row on the Project page. Download saves the whole
project as one JSON file, ushabti-{KEY}-{YYYY-MM-DD}.json, the day being the project’s own. It
holds the properties with their options, the views with the team’s filters and sort, the members,
the invites, and every live and archived task with its values, checklist, comments and blockers.
A deleted task is not in it, and neither is anybody’s own filter. See
GET /api/projects/{projectId}/export for
what is in the file and what is not.
How a destructive action asks
Section titled “How a destructive action asks”The board has no dialogs, so a destructive control turns its own row into the question — and the question names the cost in real numbers.
Delete Labels? 5 options and 14 values go with it. — Yes, delete · Cancel
Those numbers are counted, not estimated. The full set:
| Action | The question |
|---|---|
| Delete a property | Delete Labels? 5 options and 14 values go with it. |
| Delete an option | Delete Doing? 14 tasks lose it. |
| Reset the card view | Reset the card view for everyone? 3 rows go back to the default. |
| Delete a view | Delete the view Phases? The tasks stay; only this way of looking at them goes. |
| Remove a member | Remove Ada? They lose the board; their tasks and comments stay. |
| Leave a project | Leave this project? Only the owner or an admin can put you back. |
| Make owner | Make Ada the owner? You become an admin. |
| Remove an agent | Remove Builder? Its tokens stop working at once. Its runs, its comments and its activity stay on the tasks. |
| Revoke a token | Revoke this token? Builder stops working within one request. |
| Delete a webhook | Delete this webhook? example.com/ushabti stops being called, and its deliveries go with it. |
| Roll a secret | Roll the secret? Every delivery is signed with the new one from now on, and a receiver that has not been told it will refuse them. |
The Project page
Section titled “The Project page”Name and Key, owner and admins, both saving on blur. Everybody else sees “Only the owner or an admin can change the name and the key.”
The key is uppercased as you type, accepts A–Z and 0–9 only, and stops at six characters. It is
the prefix on every task key — USH-14 — and a task never stores its own key, it is built from the
prefix. So changing it renames every task at once, and the page warns the moment the box differs:
⚠ 40 tasks are called
USH-…today. Leaving this box renames all of them. Links and agent instructions that use the old key stop working.
Done when, owner and admins, is what this project calls over: a select property, then one of its options. It has one job — a task that blocks another stops blocking when it reaches this.
A new project starts with Status, Done, the last option of the Status it is made with, so Ship, blockers and parts work from the first day. Archived always counts whatever else is set, and Archived only turns the rest off. Status is still a property the owner may rename or delete tomorrow, so the project names the option it means rather than the board guessing. Delete that property or that option and the setting falls back to archived by itself; nothing has to be tidied up.
Both boxes save the moment they change. Picking a property asks the question and the option answers it, so nothing is saved in between.
Time zone, owner and admins, saving on blur, is the zone this project’s day is worked out in — an
IANA name such as Europe/Berlin, America/New_York or UTC, which is where every project starts.
The note under the box says which day it is there right now.
It has one job, and it is the same shape of job: a filter can say Due this week or Overdue, and a window of days needs a day to be counted from. That day is the project’s and not the reader’s. Two people in two zones looking at one view would otherwise see different cards, the board is drawn on the server before any browser sees it, and an agent has no browser at all.
The box takes any name the server can work a day out in, which is every name your own computer will
show you: the current spellings and the old ones alike (Asia/Kolkata and Asia/Calcutta,
Europe/Kyiv and Europe/Kiev), the fixed offsets (Etc/UTC, Etc/GMT+12, GMT), and any case
you type it in. The row keeps the spelling you used. A name it cannot use is refused in one line —
No time zone is called Europe/Atlantis. Use a name like Europe/Berlin or UTC. — and nothing is
saved. Everybody else sees “Only the owner or an admin can change the time zone of this project.”
Deleting the project owner only
Section titled “Deleting the project ”Its own block, and it does not take a click:
The board, its 40 tasks, its properties, its views and its agents go with it. There is no undo.
Press Delete project and it asks you to type the project key — USH — into a box.
Delete for good stays disabled until it matches exactly.
Your own account
Section titled “Your own account”Behind your avatar, not in project settings: /account.
- Name — what cards, comments and the activity log call you.
- Colour — eleven swatches, each wearing your initials so you can see how it will look on a card. “Pick one nobody else on your team is using.”
- Email — read only. It is how you sign in and it cannot be changed yet.
- Password — the one you use now, the new one, at least eight characters. Changing it signs every other session out.
- Other sessions — “2 other sessions are signed in”, and Sign out everywhere.