Skip to content

Administration

Roles and permissions in API Security & Integration

Each role in API Security & Integration: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to API Security & Integration as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 5 min readReport a problem
On this page
  1. Roles
  2. Integration architect
  3. API owner
  4. Information security officer
  5. Core and mainframe owner
  6. Auditor or examiner (read-only)
  7. Moraph integration engineer
  8. Permissions at a glance
  9. How access is controlled

Who can see and do what in API Security & Integration. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in MuleSoft as part of the managed service.

Roles

Integration architect

Enterprise architect, integration lead, head of digital architecture. Sets the design standards for APIs and integrations and makes sure new work fits them.

  • Sees: All API specifications, versions and their consumers; Integration dashboards across environments; Change requests and release history
  • Does: Approves API specifications before build; Sets naming, versioning and layering standards; Reviews designs that touch core and mainframe systems; Prioritizes the integration backlog with Moraph; Approves production releases where your process requires it
  • Cannot: Approve partner access without the security officer; Change security policies on their own authority
  • Approvals: Approves specifications and releases; partner access and policy exceptions also need the security officer.
  • Notified about: Specifications waiting for approval, releases scheduled, and incidents affecting integrations.

API owner

Digital banking product owner, partnership manager, payments product manager. Answers for a business-facing API: who uses it, what data it exposes, and whether it meets the partner's needs.

  • Sees: Their APIs, their consumers and usage; Errors and response times for their APIs; Partner access requests for their APIs
  • Does: Defines the business need and data scope; Sponsors partner access requests; Reviews usage with partners; Requests changes and new versions
  • Cannot: Grant partner access without security approval; Deploy changes to production; See APIs owned by other teams unless granted
  • Approvals: Partner access to their APIs is approved by them and by the information security officer.
  • Notified about: Access requests for their APIs, incidents and error spikes on their APIs, and version retirements.

Information security officer

CISO, information security officer, IT risk manager. Makes sure every API and partner connection meets your security standards and third-party risk process.

  • Sees: Policies applied to every API; Registered partner applications and their scope; Security events such as blocked requests and authentication failures; Policy exceptions and their expiry
  • Does: Sets required policies by data classification; Approves or rejects partner access; Approves and reviews policy exceptions; Certifies periodic access reviews; Directs response to security events
  • Cannot: Deploy integrations or change runtime configuration directly; Approve an exception they requested themselves
  • Approvals: Approves partner access, policy changes and exceptions.
  • Notified about: Access requests, policy exceptions coming up for renewal, security events above the threshold you set, and access reviews due.

Core and mainframe owner

Core banking manager, mainframe systems manager, application owner. Owns the systems the APIs call and protects their stability.

  • Sees: Integrations that call their systems; Traffic volumes and error rates against their systems; Changes scheduled that affect their systems
  • Does: Provides interface definitions and test access; Approves changes that touch their systems; Agrees capacity limits for traffic to their systems; Takes part in incident response when their systems are affected
  • Cannot: Register partners or issue credentials; Change gateway policies
  • Approvals: Approves integration changes that call their systems.
  • Notified about: Changes affecting their systems, incidents involving their interfaces, and traffic approaching agreed limits.

Auditor or examiner (read-only)

Internal auditor, IT auditor, regulatory examiner (under temporary access). Reviews who could access what through the APIs and how changes were controlled.

  • Sees: Partner applications, scopes and approval records; Policies on each API and their change history; Release records within the scope granted
  • Does: Reads records within their scope; Exports reports they have been given access to
  • Cannot: Change, approve or delete anything; See message contents or credentials
  • Approvals: Their access is approved by the information security officer, with a scope and an end date.
  • Notified about: Nothing by default.

Moraph integration engineer

Moraph managed-service engineer, MuleSoft developer, platform operations. Builds, deploys and operates your integrations under change and access approvals your organization gives.

  • Sees: Integration code, configuration and deployment settings; Monitoring, logs and alerts, with sensitive fields masked where configured; Change requests and approvals
  • Does: Builds and tests integrations to approved specifications; Applies policies approved by your security officer; Registers partner applications once approved; Triages alerts and restores service on the integration layer; Plans and applies runtime upgrades; Prepares the monthly service review
  • Cannot: Approve partner access, policy exceptions or production releases; Change core or mainframe systems; Deploy to production without an approved change, except to restore service under your incident process
  • Approvals: Production changes are approved by your integration architect or change board; access and policy changes by your security officer.
  • Notified about: Alerts, failed deployments, platform service notices, and change requests raised.

Permissions at a glance

ActionArchitectAPI ownerSecurityCore ownerAuditorMoraph eng
Approve an API specificationApprovesViewViewView––
Build and test integrationsView––––Full
Approve a production releaseApproves––Approves––
Deploy to production–––––Full
Change security policies––Approves––Full
Approve partner access–ApprovesApproves–––
Register partner applications–––––Full
View monitoring dashboardsViewOwn workViewOwn work–Full
View partner scopes and approvalsViewOwn workFull–ViewView
View change and release historyViewOwn workViewOwn workViewView
Manage platform users and roles––Approves––Full

"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.

How access is controlled

  • Separation is built into the service: Moraph engineers build and deploy, but production releases, partner access and policy exceptions are approved by named people at your organization.
  • Roles are set up with you during onboarding and can be limited by business line, API or environment, so teams see only what they are responsible for.
  • Every partner approval, policy change and release is recorded with who approved it, and access reviews cover both partner applications and platform users, including Moraph accounts.
  • Staff sign in through your identity provider. Auditors and examiners get temporary read-only access with a defined scope and an end date.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.