Built-In Member-Level Read-Only Role Enforced Server-Side
P
Per Kristian J. Fjellby
Add a built-in read-only role at Member level that has the same visibility as a Member, with entity writes and action and workflow execution denied on the server side. The restriction should apply to every access path, including the REST API and the Port MCP server, and be assignable to users and service accounts. Today, giving a service account read-only access at Member level means removing the Member grant from every blueprint and action and re-granting it to human users through teams. This is impractical at scale and error-prone. Entity create, update and delete, and action and workflow execution, should be rejected with a permissions error, with no per-blueprint or per-action configuration needed.