Help Center / Plutio Pal (AI) /
AI context and workspace access
Plutio Pal's access to workspace data follows the same permission model as the user asking the question. A team member with access to three projects only receives answers that reference those three projects, and records outside that scope don't appear in responses.
Role-based access
Permissions are role-based, and Plutio Pal respects those boundaries. A custom role with view-only access to invoices but no access to proposals means Plutio Pal answers invoice queries but won't return any proposal data. The same query asked by a workspace owner returns results across everything, because the owner role carries full access. Plutio Pal never elevates permissions or bypasses role restrictions.
Client access
Client users don't have access to Plutio Pal. The AI assistant works for workspace owners and team members only. Client-facing portals and shared projects don't expose the AI panel to external users.
Data privacy
Workspace data queried through Plutio Pal stays within the platform. Queries and responses aren't used to train AI models, and workspace records aren't sent to external services beyond what's needed to process the query. Conversations with Plutio Pal aren't stored as training data or shared across workspaces.
Conversation scoping
Each Plutio Pal conversation is private to the user who started the conversation. Questions asked by one team member aren't visible to other team members, and conversation history doesn't carry between users, so sensitive queries about financial data, client details, or internal project notes stay between the user and the assistant.
