> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

AI security and data controls

Port is committed to developing AI responsibly, maintaining high standards of data privacy and security across all our AI interfaces. This page addresses common questions about security, data handling, permissions, and controls for Port's AI capabilities.

Data access & permissions​

Controlling access to Port AI​

Access to Port AI is controlled through the _ai_invocations blueprint's permissions. Users need the Read, Register, and Update permissions on AI invocation entities to access and use Port AI interfaces. By configuring these, you can manage which users in your organization have access to Port AI features, including the Port AI Assistant, AI Chat Widgets, and API-based interactions.

To configure who can access Port AI:

  1. Navigate to the Data model page in Port.
  2. Search for the _ai_invocations blueprint.
  3. Go to the Permissions tab.
  4. Under the Entities section, configure the Read, Register, and Update permissions. Only users with all three permissions will have access to Port AI.
Manage AI Invocation permissions JSON configuration modal
All three permissions are required

A common mistake is granting only the Register permission, or only Register and Read, to members. This will result in a "missing permissions to manage AI invocations" error during use. Make sure to grant Read, Register, and Update permissions so users can view invocations and Port AI can write back results to the invocation record.

Isolate AI records per user​

You can grant Members access to Port AI while limiting them to their own records. Apply a dynamic permission policy to both _ai_invocations and _ai_conversation. Each blueprint has an asked_by relation to the user who initiated the interaction or conversation.

  1. Go to the data model page and select _ai_invocations.

  2. Open Permissions, select Entities, and click Edit JSON.

  3. Remove Member from the roles arrays for entities.read, entities.register, and entities.update. Keep any administrative access your organization requires.

  4. In each of those three scopes, set policy to the following query:

    {
    "combinator": "and",
    "rules": [
    {
    "property": "asked_by",
    "operator": "=",
    "value": {
    "context": "user",
    "property": "$identifier"
    }
    }
    ]
    }

    The query compares the record's asked_by relation with the current user's identifier.

  5. Set ownedByTeam to false for these scopes and remove any other role, user, or team grants that give the Members you intend to isolate unrestricted access. Click Save.

  6. Repeat these steps for _ai_conversation.

Broad grants bypass the policy

Port grants access when any applicable permission check passes. Leaving Member in a scope's roles array gives Members access independently of the policy. Removing the role grant does not disable Port AI when the policies grant the required Read, Register, and Update permissions on each user's own records.

The policy applies to existing records as well as new ones. Records without an asked_by relation matching the current user do not satisfy the policy. AI invocation records cannot be deleted; use permissions to control access to them.

Validate the policy​

  1. Test with two separate browser sessions signed in as different Members, without administrative or other broad grants. In each session, start a conversation and send a follow-up message to verify that creating, reading, and updating your own AI records still works.

  2. Confirm that each user can access their own existing and new conversations and invocations, and cannot access the other user's records.

  3. Use the permission simulator on both blueprints to check Read and Update for each user's own records and the other user's records. If access to another user's record succeeds, review the granting path and remove the remaining broad grant.

Data privacy & retention​

Human oversight & autonomy​

Rate limits & usage controls​

Port AI operates with specific rate limits and monthly quotas to ensure fair usage across all customers. For detailed information about current limits, quotas, monitoring your usage, and what happens when you reach a limit, see Limits and quotas and AI invocations.

Managed infrastructure only

These limits apply when using Port's managed AI infrastructure. Bring your own LLM provider to use your provider's limits instead.

Compliance & security standards​

Troubleshooting & support​