Settings and permissions for Actions

Who can do what

Permissions on Actions follow a simple pattern — admins can do anything, and everyone else can generally act on their own contributions.

Permissions are checked both when the page loads and when you try to act, so if you don't have permission to do something you simply won't see the button for it — rather than clicking and getting a denied message.

Configuring Action types

Action types are managed at Settings > Action Types in the main settings navigation. The list lives at company level, so every project sees the same set of types.

Adding a new type, renaming one, or removing one takes effect across the whole company straight away. There's no need to re-deploy or restart — the next time anyone opens the create form, they'll see the updated list.

See types and priorities for how the configured types are used day-to-day, and Action Types (settings) for the settings page itself.

Configuring Kanban columns

The Kanban board's column visibility and order aren't global settings — they're per-user preferences. You change them from the Manage Columns button on the Kanban view itself, not from the main settings navigation.

This means every user can have their own Kanban layout. If you never use Rejected, hide it. If you want In Progress to sit in the middle rather than the second position, drag it there. Your changes only affect your own view — everyone else still sees their own preferred layout.

See moving Actions through the Kanban board for how to open the Manage Columns dialog.

Large image handling

When you upload a very large image to the markup editor (either on an attachment or in the bulk-create flow), it's automatically scaled down for display before the editor opens. This keeps the editor responsive even on huge inspection photos that would otherwise take a noticeable amount of time to render.

The important thing to know: the original file is still uploaded at full resolution. Only the version you see in the editor is scaled. When you open the attachment later, you see the full-resolution image.

You don't need to confirm anything or wait for the resize — it happens silently before the editor opens.

Activity log visibility

Anyone who can view an Action can see its full activity log, including every status change, comment, attachment, and reassignment. The Activity tab is read-only — you can't hide individual events or edit them.

Comments inside the activity log can be edited or deleted by their author (or by an admin), following the same rules as comments elsewhere.

What's not in settings

A few things you might expect to find that don't exist for Actions:

• Automated workflows — there's no "auto-close after 30 days" or "escalate to High after 24 hours" engine
• Custom fields — only the built-in fields (title, description, priority, type, project, due date, assignees, watchers, closure details)
• SLA tracking — due dates exist, but there's no SLA breach report
• Quick-create templates — every Action is raised from a blank form
• Outbound webhooks — Actions don't fire events to external systems

If any of these would make your workflow easier, they're things to raise with your Project Commander contact as future improvements.

Next steps

• Action types and priorities — for the type configuration this page references.
• Action Types (settings) — the settings page for managing the type list.
• Managing permissions — for the broader permissions system that gates who can do what.