Why can't I set per-status field permissions or action buttons on a board inside an app?

Short answer: Boards don't have configurable action buttons, and per-status field settings are a standalone board feature. Inside an app, control access through roles and view permissions instead.

Why it happens

• Board forms always show the default Submit and Discard options. Unlike process steps, they have no action button settings.
• On a standalone board, Field settings lets you make each field editable, read-only, or hidden per status. Boards inside apps don't offer per-status field settings.

How to fix it

If you need per-status field permissions:

1. Build the board as a standalone board.
2. Set each field's permission per status in Field settings.

If the board must stay inside the app:

1. Share the board with app roles using Read-only, Initiate, Edit, or Manage. See board roles and permissions.
2. Share board views with roles as Read-only or Edit. See board views in apps.
3. Preview with each role before deploying.