All Posts
ConnectorsOctober 8, 2026 · 9 min read

How to Govern Applications Without SCIM or Provisioning APIs

A business-critical application may have no SCIM endpoint, no provisioning API and no straightforward way to automate access changes. Its administrator can still create accounts, assign roles and disable users—b...

How to Govern Applications Without SCIM or Provisioning APIs

A business-critical application may have no SCIM endpoint, no provisioning API and no straightforward way to automate access changes. Its administrator can still create accounts, assign roles and disable users—but every action requires someone to open the application and complete the process manually.

For enterprises, that creates an ongoing burden: delayed onboarding, repeated service-desk tasks and access that can remain active after employees or contractors leave.

Citadel Identity360 provides several ways to bring these applications into identity governance. Alongside connectors, directories, databases and file-based integration, Citadel supports Robotic Process Automation, or RPA, to integrate applications through their user interfaces.

This is a practical differentiator for enterprises with legacy and proprietary systems. An application’s administrator interface can become a route for automated fulfillment, while Citadel governs the request, approval, lifecycle event and verification.

The business can extend access control to the systems it already depends on.

Why Applications Without SCIM Still Need Governance

SCIM provides a standardized protocol for managing identity resources. It simplifies integration when an application supports it.

Many enterprise applications, however, use other administration methods: local accounts, directory groups, database records, batch imports or administrator screens.

These systems still require answers to the same questions:

  • Who has access?

  • Which permissions do they hold?

  • Who approved those permissions?

  • Does the access remain appropriate?

  • What happens when the person changes roles or leaves?

  • How is a completed removal verified?

A disconnected application can participate in governance through collected access data and controlled fulfillment. RPA adds another opportunity: automate repeatable administrator actions where the user interface provides the available change path.

The Citadel Differentiator: Connectors and RPA Working Together

Citadel’s integration framework supports REST, SOAP, LDAP, JDBC, file exchanges, scheduled feeds, mainframe and custom integration patterns.

RPA extends this approach to applications whose access administration takes place through screens.

For configured application workflows, RPA can perform approved steps such as creating an account, changing a role or disabling access. The workflow follows the application’s supported administration process.

The read and change paths can also differ. For example, Citadel can receive account information through a scheduled export while RPA performs approved changes through the administrator interface.

Integration path Typical application capability Role in governance
API or standard connector Supported service interface Read access information and execute supported lifecycle changes
LDAP or JDBC Directory or database access Collect relevant records and perform supported operations
Files and batch exchanges Export or import functionality Aggregate access data and coordinate scheduled changes
RPA integration Administrator interface with repeatable actions Automate configured account and permission changes through the UI
Governed manual fulfillment Administrator action requiring human handling Assign, track and document the change

This flexibility lets Citadel match the integration approach to the application while maintaining a consistent governance process.

Six Steps to Govern Applications Without SCIM

1. Establish Ownership and the Integration Paths

Start with the application’s business owner, technical owner and access administrator.

Identify where accounts and permissions are maintained, which access is sensitive and how workforce or contractor status reaches the governance process.

Then map three requirements:

Read: How will account and entitlement information be collected?

Change: Will fulfillment use a connector, batch import, directory operation, RPA workflow or administrator task?

Verify: What observation will establish that the requested change took effect?

These paths need not use the same technology. A legacy application might provide a reliable CSV export while offering account administration only through its UI.

That combination creates a useful Citadel integration pattern: file-based visibility with RPA-based fulfillment.

2. Build a Reliable Account and Entitlement Feed

Governance decisions need current, understandable access information.

A practical export should include stable account identifiers, account status, correlation attributes, roles or permissions and the extraction time. Its scope should make clear whether it represents a full snapshot or a partial population.

Include privileged accounts and service accounts where relevant. Define how duplicates, renamed users, multiple roles and missing values will be handled.

Citadel’s file, directory and database integration options provide routes for bringing this information into governance.

Feed validation belongs in the onboarding design. A truncated export or stale snapshot should prompt investigation before decisions are made from incomplete data.

Reliable observations support reviews and provide a way to check the outcome of subsequent changes.

3. Connect Accounts with Accountable Identities

Application accounts become more useful when they are linked to the people or services behind them.

Citadel brings account and entitlement information into a shared identity model. This supports identifying access associated with departed employees, expired contractors, missing owners or responsibilities that have changed.

Non-human accounts need their own ownership and purpose. A service account supporting a production integration should follow the lifecycle of that service.

Contractor accounts should remain connected to sponsorship and engagement dates.

Unmatched accounts require investigation. They may represent mapping problems, shared accounts or legitimate services needing an owner. Correlation creates the context for choosing the correct action.

4. Apply Policy and Use RPA for Approved Fulfillment

Access decisions should follow the organization’s approval and policy requirements, regardless of how the application is administered.

Citadel’s lifecycle and access workflows coordinate the decision:

  • A joiner receives access appropriate to the approved role.

  • A mover’s new permissions and obsolete access are considered together.

  • A leaver triggers the relevant removal activities.

  • A contractor’s access follows the engagement and approved extensions.

For an application integrated through RPA, the approved outcome can be fulfilled through a configured UI workflow.

This is where RPA provisioning and deprovisioning become valuable. A repeated administrator procedure becomes an automation path connected to governance.

Where an action needs human handling, Citadel can route a fulfillment task to the responsible administrator. Exceptions can therefore remain within the same operating process.

RPA workflows should be maintained when application screens or procedures change. A clearly assigned owner keeps the automation usable over time.

5. Verify the Change and Preserve Evidence

Verification completes the governance process.

After a grant or removal, the application’s observed state should be compared with the approved outcome. That observation may come from a fresh export, directory read, supported database query or reviewed administrator evidence.

For RPA fulfillment, successful execution should be paired with confirmation of the resulting access state.

The evidence should connect the request or lifecycle event, approval, fulfillment action, timestamps, verification result and any unresolved exception.

This supports audit readiness by making the sequence understandable. Teams can explain who authorized a change, how it was performed and what confirmed the outcome.

6. Include the Application in Recurring Access Reviews

Once ownership and access information are available, the application can participate in access certifications.

Reviewers need enough context to assess current permissions against business responsibilities and risk.

A rejected entitlement can then enter the appropriate fulfillment path—connector, batch, RPA or administrator task—with subsequent verification.

This connects review decisions with operational action. Legacy applications become part of the same access-review discipline as modern services.

A Practical Example: RPA Offboarding for a Legacy Finance Application

Consider an illustrative finance application that provides a daily account export and an administrator portal, but no provisioning API.

An employee leaves the organization.

The Citadel-based process can be configured to:

  1. Receive the departure event and identify the employee’s application account.

  2. Initiate the required removal workflow under the organization’s policy.

  3. Use RPA to complete the approved disablement steps in the administrator portal.

  4. Check the account’s status through a fresh observation.

  5. Record completion or route an unresolved exception for follow-up.

The application continues operating as before. Its access administration becomes connected to the enterprise lifecycle process.

For a mover, the same approach can support removing an obsolete role and assigning approved new access. For a contractor, the engagement end date supplies the lifecycle trigger.

Why This Matters for Hybrid Enterprises

RPA application integration broadens the routes available for bringing difficult systems under governance.

For enterprises, the potential benefits are concrete:

  • Less repetitive administration: Configured RPA workflows can perform repeatable access tasks.

  • Broader lifecycle coverage: Legacy application access can follow employee and contractor events.

  • More actionable reviews: Rejected permissions have an identified fulfillment path.

  • Continued use of essential systems: Governance can improve while application modernization proceeds separately.

  • Clearer accountability: Owners, decisions, actions and verification remain connected.

Citadel also supports no-code administration and includes 400 hours of customization support for organization-specific requirements such as workflows, approval logic and integration adaptations. These capabilities are described in Citadel’s platform overview and commercial comparison.

The same wider governance platform covers people and non-human identities. Its agent and MCP governance adds ownership, specific tool authorization and controlled agent usage as the enterprise adopts AI.

Put Your Hardest Application into the Demonstration

Choose an application that currently depends on administrator screens or recurring manual tickets.

Bring its account export, access-administration procedure and one lifecycle scenario: a joiner, role transfer or departure.

Then follow the process through Citadel—from identity information and policy to RPA fulfillment and verification. You can also watch Citadel demonstrations to explore the wider platform.

An application without SCIM can still have an automated, accountable governance process. Citadel’s combination of connectors, RPA and governed fulfillment provides the routes to build it.

Explore Citadel Identity360 and request a demonstration around your most difficult legacy application.

Frequently Asked Questions

Can Citadel govern an application without SCIM?

Yes. Citadel supports API, directory, database, file, batch and custom integration methods, alongside RPA and governed manual fulfillment.

How does Citadel use RPA for application integration?

RPA can execute configured, approved access-administration steps through an application’s UI. This provides a fulfillment path where a usable provisioning API is unavailable.

Can file-based visibility work with RPA provisioning?

Yes. Account and entitlement data can be collected through an export while RPA performs approved changes through the administrator interface. A subsequent observation supports verification.

Can RPA support deprovisioning?

Yes. Configured RPA workflows can perform supported disablement or permission-removal procedures, with the outcome checked through the verification path established for the application.

Does a file export provision access by itself?

No. An export provides observed information. Changes require an inbound interface, connector, RPA workflow or administrator action.

What happens when an action needs manual handling?

Citadel’s governed fulfillment process can assign the action to an accountable administrator and track its outcome, preserving the connection between the decision and completion evidence.

Stay Current

Get the latest insights delivered

Compliance updates, IGA best practices, and regulatory analysis from Astranova Labs.

Browse all posts →