MultiPartyApprovalFullAccess

Summary

Provides full access to Multi-party approval, plus related permissions to AWS Organizations and AWS IAM Identity Center for managing approval teams and identity sources. The Multi-party approval User Guide says it grants broad permissions to manage all aspects of multi-party approval workflows.

Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.

Identity

ARN

arn:aws:iam::aws:policy/MultiPartyApprovalFullAccessCopy ARN

Default version

v6

Created

2025-06-18

Last edited

2026-02-12

Services

kms, mpa, organizations, sso, sso-directory

Control-plane actions (41)

By access level: 9 List, 2 Permissions management, 12 Read, 2 Tagging, 16 Write.

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: mixed.

Can be attached: Yes, to users, groups and roles.

Why this tier

• Grants at least 80% of the write and permissions-management actions of: mpa (11 of 11).

Guidance

Related policies

Same service

• AIOpsConsoleAdminPolicy
• AmazonBioDiscoveryFullAccess
• AmazonBioDiscoveryInAppFullAccess
• AmazonHoneycodeServiceRolePolicy
• AWSControlTowerIdentityCenterManagementPolicy
• AWSGrafanaWorkspacePermissionManagement
• AWSGrafanaWorkspacePermissionManagementV2
• AWSManagedAccountUserEntitlementAccess

Same domain

• AccessAnalyzerServiceRolePolicy
• AccountManagementFromVercel
• AlexaForBusinessNetworkProfileServicePolicy
• AmazonAppStreamPCAAccess
• AmazonChimeServiceRolePolicy
• AmazonCloudDirectoryFullAccess
• AmazonCloudDirectoryReadOnlyAccess
• AmazonCloudWatchEvidentlyReadOnlyAccess

Frequently asked questions

When should I attach MultiPartyApprovalFullAccess?

The reference page says you can attach MultiPartyApprovalFullAccess to your users, groups and roles, and describes it as: provides full access to Multi-party approval and related permissions for approval teams and identity sources. Attach it where administering Multi-party approval is the intended scope.

What does MultiPartyApprovalFullAccess grant?

It allows mpa:* on all resources, two AWS Organizations read actions, IAM Identity Center application actions (create, describe, delete, grants, authentication methods and access scopes), sso and sso-directory read actions, and kms:Decrypt under IAM Identity Center and identity store conditions.

What are the security risks of MultiPartyApprovalFullAccess?

mpa:* allows every Multi-party approval action, and the policy includes IAM Identity Center application create and delete actions. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "MpaFullAccess",
      "Effect": "Allow",
      "Action": [
        "mpa:*"
      ],
      "Resource": "*"
    },
    {
      "Sid": "OrganizationsAccess",
      "Effect": "Allow",
      "Action": [
        "organizations:ListDelegatedAdministrators",
        "organizations:DescribeOrganization"
      ],
      "Resource": "*"
    },
    {
      "Sid": "SSOCreateApplication",
      "Effect": "Allow",
      "Action": [
        "sso:CreateApplication"
      ],
      "Resource": [
        "arn:aws:sso:::instance/*",
        "arn:aws:sso::aws:applicationProvider/mpa"
      ]
    },
    {
      "Sid": "SSOApplicationManagement",
      "Effect": "Allow",
      "Action": [
        "sso:DescribeApplication",
        "sso:PutApplicationAssignmentConfiguration",
        "sso:PutApplicationGrant",
        "sso:PutApplicationAuthenticationMethod",
        "sso:PutApplicationAccessScope",
        "sso:DeleteApplication"
      ],
      "Resource": "*",
      "Condition": {
        "StringEqualsIfExists": {
          "aws:CalledViaLast": "mpa.amazonaws.com"
        }
      }
    },
    {
      "Sid": "SSOManagementAccess",
      "Effect": "Allow",
      "Action": [
        "sso:DescribeInstance",
        "sso:DescribeRegisteredRegions",
        "sso:GetSharedSsoConfiguration",
        "sso-directory:DescribeUsers",
        "sso-directory:SearchUsers",
        "sso:ListInstances"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AllowKmsAccessViaIdentityCenter",
      "Effect": "Allow",
      "Action": [
        "kms:Decrypt"
      ],
      "Resource": "*",
      "Condition": {
        "ArnLike": {
          "kms:EncryptionContext:aws:sso:instance-arn": "arn:*:sso:::instance/*"
        },
        "StringLike": {
          "kms:ViaService": "sso.*.amazonaws.com"
        }
      }
    },
    {
      "Sid": "AllowKmsAccessViaIdentityStore",
      "Effect": "Allow",
      "Action": [
        "kms:Decrypt"
      ],
      "Resource": "*",
      "Condition": {
        "ArnLike": {
          "kms:EncryptionContext:aws:identitystore:identitystore-arn": "arn:*:identitystore::*:identitystore/*"
        },
        "StringLike": {
          "kms:ViaService": "identitystore.*.amazonaws.com"
        }
      }
    }
  ]
}

Version history

Current version v6, edited by AWS on 2026-02-12. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/MultiPartyApprovalFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/MultiPartyApprovalFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/MultiPartyApprovalFullAccess

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/MultiPartyApprovalFullAccess

resource "aws_iam_role_policy_attachment" "multipartyapprovalfullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/MultiPartyApprovalFullAccess"
}

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("MultiPartyApprovalFullAccess"),
);

Sources

• MultiPartyApprovalFullAccess (AWS Managed Policy Reference Guide) (retrieved 2026-11-13; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
• AWS managed policies for Multi-party approval (retrieved 2026-11-13; supports summary, bestPractices, securityConsiderations, faqs)
• Managed policies and inline policies (IAM User Guide) (retrieved 2026-11-12; supports securityConsiderations, faqs)
• AWS managed policies for job functions (IAM User Guide) (retrieved 2026-11-12; supports faqs)

• Official AWS reference for MultiPartyApprovalFullAccess
• AWS service guide
• Report a data issue