Integration

SAP Integration Suite Access Policies: How to Restrict Cloud Integration Access per Team

Vlado Balko

How access policies in SAP Integration Suite let you say: everyone in-house can work on everything, and each partner team only on the packages you hand them.

Here is the uncomfortable truth about Cloud Integration authorizations: roles are tenant wide. If you hand someone WorkspacePackagesEdit so they can build an integration flow, they can edit every integration flow on the tenant. Your payroll interface, your bank connectivity, the flow that took three weeks to get right — all of it, one click away from whoever joined the project this morning.

That is fine while the tenant belongs to one team. It stops being fine the moment a second party starts working in it: a system integrator, a software vendor’s implementation team, or another consultancy delivering a project alongside yours. The answer is access policies, and they live in a place most people never look: Monitor → Manage Security → Access Policies.

How to access reaches an artifact

What an access policy actually does

An access policy is a named bucket of references. Each reference is a rule like “every integration flow whose name matches .* " or "the integration package named PARTNER_Invoice_Automation ". Any artifact caught by a reference becomes protected: only users who hold the policy's role may create, edit, deploy, delete it or see its runtime data. Everyone else keeps read access — they can open the flow and look at it, but every action is greyed out.

Two things follow from that, and both matter:

A policy restricts, it does not grant. The moment an artifact is covered by a policy, everyone without the matching role loses write access to it — including your own people.

Policies OR together. If an artifact is covered by three policies, holding any one of the three roles is enough. That is what makes the pattern below work. How access reaches an artifact

The chain from a user to an artifact

The plumbing is four links long, and the join between link three and four is a plain string that nobody validates for you.

  1. A user sits in a role collection ( PI_External_Developer ).

  2. The role collection contains a custom role built from the role template CustomRoleTemplate of application it (that's Cloud Integration).

  3. That custom role carries the attribute custom_role , source Static, value ExternalPackages .

  4. ExternalPackages is the Role Name of the access policy.

Configure Attributes

The custom_role attribute on the role

Type the value differently in the two places and nothing breaks visibly — the policy simply protects its artifacts from everybody, forever, and you will spend an afternoon wondering why.

Once created, custom roles show up in the subaccount like any other role:

Custom roles in the subaccount

Scenario 1 — the in-house team may do everything

Counterintuitively, the way to open the tenant up is to lock it down first. Create one policy — call it AllArtifacts — and give it one reference per artifact type, each with Attribute: Name, operator Matches, expression .* :

A catch-all reference

Repeat for every type you care about. The type list is longer than you’d think — integration flows, script collections, message and value mappings, OData, REST and SOAP APIs, message queues, data stores, global variables, and the Integration Advisor types:

The artifact types you can protect

Seven references cover what a normal Cloud Integration team builds:

The AllArtifacts policy with its references

Then create the custom role AP_AllArtifacts with custom_role = AllArtifacts and drop it into the role collection your own developers already have. From their side nothing changes: they keep editing everything, exactly as before.

The in-house role collection

For everybody else the tenant has just turned read-only.

Scenario 2 — a partner team, scoped to its own packages

Now the partner team. They get a minimal role collection — read, edit, configure, deploy, monitor — and deliberately not the AP_AllArtifacts role:

The partner role collection

Then a second policy, ExternalPackages , whose references are whole packages rather than artifact types:

A package-level reference

One reference per package you decide to open to them:

The ExternalPackages policy

Its role AP_ExternalPackages goes into the partner role collection. Because policies OR together, artifacts inside PARTNER_Invoice_Automation are now reachable by two groups: your own people through the catch-all, and the partner team through the package policy. Everything else on the tenant stays read-only for the partner. Two policies, two audiences

Adding a team later is a five-minute job: new policy, new custom role, new role collection, one reference per package.

Five things that will bite you

Package references only support “equals”. For artifact types you get a regex ( Matches ), but for Integration Package the operator is fixed to Equals — the radio button is read-only. No PARTNER_.* shortcut; you list the packages by name, one reference each. Pick a naming convention early and expect to maintain the list. You cannot stop anyone from creating packages. WorkspacePackagesEdit means "create, edit, import, export, delete a package with its artifacts" — SAP does not split the two. A partner developer can always create an empty package. What the catch-all policy buys you is that they cannot put anything in it, which makes the package useless. Sweep the empty shells up occasionally.

The catch-all locks out your own people too. Anyone in-house who is missing the AP_AllArtifacts role will suddenly be unable to create an integration flow, and the error message will not mention access policies. Assign the role collection before you create the policy, not after.

Roles only arrive with a new token. After any change, users must log out and back in. Half the “it doesn’t work” reports are this.

Policies are per tenant. They are not transported with your content. Whatever you build in dev has to be rebuilt by hand in test and production — which, on the upside, means you can protect production more tightly than dev.

The short version

One AllArtifacts policy with Name matches .* per artifact type, its role in the role collection every in-house developer holds.

One policy per partner team, containing Integration Package Name equals

<package> references, its role in that team's role collection.

The custom role attribute value and the policy’s Role Name must be byte-identical.

Partner developers can still create empty packages. Live with it, and sweep up. It took an afternoon to build, and it turned “we cannot give you access to that tenant” into “here is your package, go ahead”.

SMARTER TECH, SMARTER BUSINESS

Cloud, AI and mates. Integration, development, automation and AI on SAP Business Technology Platform and Microsoft.

Write to us →

RESOURCES

© 2026 CLAIMATE · CLOUD · AI · MATES

SAP PartnerEdge · Microsoft Partner

SMARTER TECH, SMARTER BUSINESS

Cloud, AI and mates. Integration, development, automation and AI on SAP Business Technology Platform and Microsoft.

Write to us →

RESOURCES

© 2026 CLAIMATE · CLOUD · AI · MATES

SAP PartnerEdge · Microsoft Partner

SMARTER TECH, SMARTER BUSINESS

Cloud, AI and mates. Integration, development, automation and AI on SAP Business Technology Platform and Microsoft.

Write to us →

© 2026 CLAIMATE · CLOUD · AI · MATES

SAP PartnerEdge · Microsoft Partner

Integration

SAP Integration Suite Access Policies: How to Restrict Cloud Integration Access per Team