[object Object]

App Engine Studio is the reason your VP of Apps is excited and the reason your platform team is nervous. Both are right. Without guardrails, citizen developers will produce apps that work, scale poorly, and bring license consequences nobody modeled.

Three categories of guardrail

Treat citizen development as a tiered program with three guardrail layers: organizational, technical, and lifecycle.

Organizational guardrails

  • Every app has a named platform-team sponsor before it can leave dev
  • Citizen developers complete a one-day enablement covering data modeling and ACL basics
  • Apps with more than 50 users escalate to platform team for review

The sponsor model is the single most important rule. It costs the platform team almost nothing and stops 80% of bad designs.

Technical guardrails

Set these in sys_properties for the App Engine scope:

sn_aes.max_tables_per_app = 8
sn_aes.max_records_default_view = 1000
sn_aes.allow_global_scope = false
sn_aes.allow_external_table_extension = false

Anyone hitting a limit lands on a platform team review. Most stay within.

A scoped role for citizen devs

Do not give citizen developers app_creator and delegated_developer globally. Build a scoped role that:

  • Allows app creation in a designated Citizen Apps parent scope
  • Disallows extending core tables (incident, change, problem)
  • Requires platform-team approval to publish to production

Lifecycle guardrails

Every citizen app needs a yearly review. If the original developer left, the app is reassigned to the sponsor. If no one accepts ownership, the app moves to archived status with a 60-day deletion window.

License math citizen developers do not see

Custom apps that grant table access to non-fulfillers may push users into a higher license tier. Build a quarterly report:

var ga = new GlideAggregate('sys_user_role');
ga.addQuery('role.scope', 'STARTSWITH', 'x_citizen_');
ga.addAggregate('COUNT_DISTINCT', 'user');
ga.query();

Cross-reference distinct users against your license tier breakdown. Surprises here drive the next renewal conversation.

What to do this week

If you are launching App Engine to a new business unit next quarter, ship the guardrails before the access. The order matters — culture forms in the first month and is hard to retrofit.

[object Object]
Share