Citizen Developer Governance for AI-Built Apps

One organization role decides who may build an AI-built app, and the documentation describes no approval step before an app is published or made Public. Nine decisions, the control behind each, and what IT still decides.

Chengjun Yuan
Chengjun Yuan
Co-founder & CTO · Nov 6, 2026

Citizen developer governance is the set of rules that decides who in a business may build software without being a developer, what they may build, and who can open, change and remove what they make. Once an AI writes the code, building an app takes a description and a few answers, so the rules stop being about skill. They come down to roles and defaults: which role lets a person build, what a new app is shared with, and what stands between a finished app and the open internet.

In Insulin Apps, one organization role decides who may build. An org ADMIN builds organization apps and personal ones, an org EDITOR builds personal apps only, and a VIEWER builds none. Beyond that, what IT inherits are defaults, not approvals: the maker starts the build with Build my app, anyone with Editor or higher on the app can publish it, and its Owner or an Admin on it can make it Public. The documentation describes no step at which someone else signs off.

The table sets out nine decisions in the order an app meets them, with the control behind each and the part left to IT. The notes after it take the rows in turn.

Citizen developer governance, decision by decision

Each decision has a control, and a question the control leaves open. The middle column is the product’s behaviour as Fours’ documentation for apps describes it. The right-hand column is the policy you write.

DecisionThe control in Insulin AppsWhat IT still decides
Who may buildAn org ADMIN builds organization and personal apps; an org EDITOR, personal apps; a VIEWER, noneWho holds org EDITOR and ADMIN, since those roles are the permission to build
Personal or organizationChosen on the Describe step and never changed. A personal app can’t be shared with teammates, but its creator is its Owner and can publish it and make it PublicWhether a personal app may ever be Public, and how you would find out
Who can open it in-houseA new organization app is shared with the whole organization as UserWhich apps start lower, or with org-wide sharing off
Who publishes, who goes PublicEditor or higher on the app publishes. The Owner or an Admin on it decides who can open the published app. New apps start Console-only; older apps start PublicWhether any app may be Public, and who may switch it
KeysThe Owner or an Admin sets Secrets; an org ADMIN or EDITOR with Editor or higher on the app can read them in the previewWho holds Editor on an app that holds a key
Fours dataA published app’s own OAuth client calls the Fours API as an Editor, for organization and personal apps alikeWhat each app’s code calls, reviewed before it is published
Production dataApp admins browse the published app’s database read-onlyWho holds Admin on an app that stores sensitive records
DeletingThe Owner, or an Admin on an organization app. An org ADMIN title on its own grants nothingWho must hold Admin so an app can be retired
Approval, audit, per-viewer dataThe documentation describes no app approval policy, no app audit log and no per-viewer data scopingYour own review step, your own record, and who an app is shared with

Who may build an AI-built app?

Whoever holds the organization role that permits it, so the first governance decision is who holds that role. Fours’ Getting Started guide defines three. An ADMIN has full access, and “only an ADMIN can act at the organization ownership level.” An EDITOR creates and manages their own agents, channels and apps but “cannot create organization-level resources.” A VIEWER is read-only on shared resources.

In the app builder those become three versions of the same New app button. An admin’s wizard preselects an organization app. In an EDITOR’s wizard, the Other people will use it too option reads Only organization admins can create apps for the organization. A VIEWER doesn’t see the button, and the wizard says You can’t create apps.

Two consequences follow for anyone writing the policy:

  • The role isn’t an app setting. EDITOR also decides who creates their own agents and channels, so granting it to one would-be maker is a workspace decision, not an app decision.
  • A team app needs an admin, or an admin’s hand-off. The one role that creates an organization app also has full access to settings. If you’d rather not grant that, an org admin can create the app and give its maker Editor on it: an org EDITOR with Editor or higher on an app can open it in the builder and change it. Weigh what Editor carries, though. It is also enough to publish the app and to read its keys in the preview.

Can a personal app reach the open internet?

Yes. A personal app can’t be shared with teammates, but its creator can publish it and make it Public. Four rules in the documentation combine to allow it:

  1. Only I will use it on the Describe step makes a Personal app, “which can never be shared,” and the choice “can’t be changed once the app is created.”
  2. A personal app’s Owner is its creator, and only “the app’s Owner or an Admin on it” can change who may open the app once it is published.
  3. “Anyone with Editor or higher on the app can publish it.”
  4. The access setting belongs to every app. Nothing in the documentation restricts Public to organization apps.

Put together, the role that lets a person build for themselves also lets them open what they built to anyone with its URL, with Editor-level access to your Fours data behind it, and the documentation names no point at which an admin is asked.

That is where the word personal misleads. Microsoft’s guidance on Power Platform environment strategy treats personal space as a place to build: it recommends guiding makers “to their own, personal environment where they can safely build their apps,” and adds: “When the resource is ready to be shared, the maker can use the continuous integration attached to the developer environment to promote it to a production environment.” In that model, reaching production is a separate step. A personal app here is personal in who can share and edit it, not in where it can run.

What to decide: whether a personal app may ever be Public, and how you would know if one is. The Apps views the documentation describes list the apps you own and the ones shared with you, so they don’t establish how IT would take an inventory of other members’ personal apps. Until you have a way to check, a rule against it rests on the people who hold EDITOR, and on asking them. A personal app also has no Owner row and can’t be transferred, so an app that became a team’s tool while personal stays with the person who built it.

Who can open an organization app by default?

Everyone in the organization, as User, from the moment the app is created. The Describe step calls an organization app one “everyone in your organization can see and run from the start,” and its sharing starts with the whole organization as User. For an app that holds customer records or pricing, lower the org-wide role to Viewer or turn it off and share by name; how to share an internal app with roles covers the default-plus-exceptions pattern.

Who can publish, and who can make an app Public?

Anyone with Editor or higher on the app publishes it, and its Owner or an Admin on it chooses who can open it. For the policy, those two roles are the decision: Editor on an app is the right to put a version into production, and Owner or Admin is the right to decide its audience, strangers included. Publishing an AI-built app as Team only or Public covers both settings, including why apps made before the setting existed start Public.

What can an app’s code use once it is published?

Your Fours data, as an Editor, and the keys in the app’s Secrets, among other things. The documentation’s section on what a published app can reach has the full picture. For a build policy, three parts of it matter:

  • Keys. The app’s Owner or an Admin sets a secret, but an org ADMIN or EDITOR with Editor or higher on the app can read its secrets in the preview. Whoever holds Editor on an app that holds a key holds the key; who can read the API keys in an AI-built app has the details.
  • Fours data. Each app gets an OAuth client of its own when it is created, and the Fours API counts that client as an Editor whatever the app’s ownership or audience. An Editor writes as well as reads, so deciding who may build is also deciding who may ship code that changes your Fours data. Review what an app calls before its first publish.
  • Production data. Once the app is published, its Owner and Admins can browse its database read-only under Settings → Database, 25 rows at a time. That gives a reviewer a way to see what the app has stored without being able to change it.

Who can delete an app?

The app’s Owner, or anyone with Admin on an organization app. An org ADMIN title on its own grants nothing. The documentation is explicit: “an org ADMIN who did not create the app needs an Admin share on it to delete it.” Deleting starts a cleanup of the app’s source and saved versions, its database and the published app.

Two things follow for a policy. An admin who may need to retire an app has to hold Admin on it, granted in advance by the Owner or an existing Admin. And before an owner leaves or changes role, have them transfer their organization apps: only the owner can transfer, only to another org ADMIN, and the transfer is refused once the owner is no longer an organization ADMIN.

What does the product leave to your own process?

An approval step, an audit trail and per-viewer data rules. The documentation describes no app approval policy, no app audit log and no per-viewer data scoping, so plan to supply each of those yourself:

  • Approval. Each documented step belongs to one person. The maker approves the plan with Build my app, and nothing is built until they do. Anyone with Editor or higher on the app can publish it, and its Owner or an Admin on it can switch it to Public through the Allow public access? confirmation. The documentation describes no second person’s sign-off at any of those steps. If your policy needs one, it happens outside the product, and it is as strong as your choice of who holds Editor, Owner and Admin.
  • Audit. With no app audit log in the documentation, keep your own record of which apps are published, which are Public and who agreed to each. Each card in the Apps window says Draft, Team only or Public, but a person sees the cards for the apps they can open.
  • Per-viewer data. With no per-viewer scoping in the documentation, decide what an app shows by who can open it. If part of its audience shouldn’t see a record, narrow the audience rather than expect the platform to hide the record from some of them.

The roles, encrypted secrets and publishing controls these decisions rest on are set out together on Insulin Apps, the AI app builder for business apps.

Sources

Primary sources for the platform rules cited above. Last verified November 6, 2026. Providers change their products, prices and terms without notice — check the source before relying on a detail.

  • Insulin Custom Apps — Fours Doc — The Creation Interview: Who is this app for? can't be changed once the app is created; Other people will use it too makes an Organization app everyone in the organization can see and run from the start, and Only I will use it makes a Personal app, which can never be shared. Ownership and Sharing: an organization ADMIN creates organization or personal apps, an EDITOR personal apps only (Only organization admins can create apps for the organization.), a VIEWER none (You can't create apps); a new organization app starts out shared with the entire organization as User; Admin granted individually only by an organization ADMIN; deletion by the Owner, or an Admin on an organization app, an org ADMIN who did not create the app needing an Admin share on it; transfer by the owner to an organization ADMIN only, refused once the owner is no longer an organization ADMIN, and a personal app having no Owner row and unable to be transferred; Edit App for an organization ADMIN or EDITOR with Editor or above on the app; deleting an app cleaning up its source, saved versions, database and the published app. The Live Preview: secrets injected into the preview of an organization ADMIN or EDITOR with Editor or higher on the app. What a Published App Can Reach; How a published app reaches your Fours data: every app's own OAuth client treated as an Editor, for organization and personal apps alike, Console-only and Public apps both getting it, the access setting deciding who can open the app, not what its code can reach, and the client deleted with the app. Publishing: anyone with Editor or higher on the app can publish it. Secrets: only the app's Owner or an Admin on it adds or removes one. Who can open a published app: Console-only (where a new app starts) or Public; apps created before the setting existed Public until someone changes them; only the Owner or an Admin on the app changing it, with a confirmation before Public. Data an app keeps for itself: app admins browsing the published database read-only, 25 rows at a time
  • Insulin Getting Started — Fours Doc — Roles and Permissions, Organization Roles: ADMIN full access and the only role that can act at the organization ownership level; EDITOR creating and managing its own agents, channels and apps, and unable to create organization-level resources; VIEWER read-only on shared resources
  • Microsoft Learn: Develop a tenant environment strategy to adopt Power Platform at scale — Guiding makers to their own, personal environment where they can safely build their apps; when a resource is ready to be shared, the maker using the continuous integration attached to the developer environment to promote it to a production environment. Page dated October 17, 2026

Browse every post on the Insulin Blog

Stay Updated

New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.

Follow Fours on LinkedIn