CRA Package Access

Key Concepts

What is Package Access Control?

Package Access Control allows CRA administrators to explicitly designate which affiliate organizations have permission to access specific packages. By default, packages are only visible to the organization that owns them. With Package Access Control, CRA organizations can extend visibility to selected affiliates on a per-package basis.

Access Model

Affiliate organizations can access packages through two paths:

1. Owned Packages: Packages created and owned by the affiliate organization
2. Granted Access: Packages owned by a CRA organization that has explicitly granted access to the affiliate

Who Can Use This Feature

CRA Organization Administrators

CRA organization administrators have full control over package access for packages they own. They can:

• Grant access to any of their affiliate organizations
• Modify existing access grants
• Revoke access from affiliate organizations
• View which affiliates have access to each package

Affiliate Organization Users

All users within affiliate organizations (Administrators, Processors, Integration Admins) can:

• View packages owned by their organization
• View packages that have been shared with their organization by a CRA
• Use shared packages in their workflows
• See which packages have been granted to their organization

Note: Affiliate users cannot create, modify, or remove access grants. Only CRA administrators can manage package access.

Managing Package Access

Granting Access to Affiliates

To grant package access to affiliate organizations:

1. In Cortex, navigate to the Package Details page for the package you want to share
2. Scroll to the Package Access Control section
3. In the Affiliate Organizations dropdown, select the organizations you want to grant access to
4. Click Save Changes to apply your selections

The selected affiliate organizations will immediately gain visibility to the package and can begin using it in their workflows.

API Usage

REST API Endpoint

When affiliate organization is creating an invite via the REST API (POST /v1/vid/invites) - Create vID Invite, they can include an optional organizationId parameter. The created invite will be associated with the specified organizationId rather than the package's organization.

{
  "packageId": "PAC-81eb7401",
  "organizationId": "ORG-4d7508482c19",
  "contactInformation": {
    "email": "[email protected]",
    "firstName": "John",
    "lastName": "Doe"
  },
  "deliveryMethod": "EMAIL"
}

Parameters:

• packageId (required): The ID of the package to use for the invite
• organizationId (optional): The ID of the organization to associate with the invite. If not provided, the package's organization will be used
• Other standard invite parameters (contactInformation, deliveryMethod, etc.)