sharing

Manage sharing permissions for tables, workflows, and agents via the Frontline CLI.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/api-evangelist/frontline --skill sharing-api-evangelist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sharing
Source: https://github.com/api-evangelist/frontline/tree/main/skills/vendor/sharing
Command: npx skills add https://github.com/api-evangelist/frontline --skill sharing-api-evangelist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Controlling who can view or edit tables, workflows, and agents in a Frontline workspace requires resolving valid user and team IDs, understanding per-resource access levels, and applying full-replace permission configurations, which is error-prone without guidance. ## Core Features & Use Cases - Permission Inspection: Read the current sharing configuration of any table, workflow, or agent, including workspace default, team and user levels, and your own effective access. - Full-Replace Configuration: Set workspace, team, and user access levels in one call, with levels tailored per resource type (FULL_ACCESS, VIEW, NONE, CAN_INTERVENE for agents). - ID Resolution: List valid account users and teams before applying permissions to avoid invalid-id errors. - Use Case: Lock down a sensitive data table so only the Sales team can view it and one analyst can edit it, by setting workspace to NONE and granting explicit team and user levels. ## Quick Start Ask the assistant to lock down table 42 so only user 5 has full access and team 3 can view it, using the Frontline sharing commands.

Frequently Asked Questions about sharing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share a table with specific users or teams in Frontline?▼

Use frontline sharing set with --entity-type table, the table id, and a JSON --data payload containing workspace, users, and teams levels. Resolve valid userId and teamId values first with frontline sharing users and frontline sharing teams.

How do I check who has access to a workflow or agent?▼

Run frontline sharing get with the entity type and id to see the workspace default level, team and user entries, and your own effective level in the myLevel field. Any user with at least VIEW access can read the configuration.

What access levels are available for tables, workflows, and agents?▼

Tables and workflows support FULL_ACCESS, VIEW, and NONE. Agents additionally support CAN_INTERVENE, which allows viewing and intervening in conversations without editing the agent. Levels are validated per resource type by the backend.

Why do I get a 403 error when setting sharing permissions?▼

A 403 on set means the caller lacks FULL_ACCESS on the resource. Only users with FULL_ACCESS, admins, owners, or the resource creator can change sharing; users with VIEW can only read the configuration.

Does sharing apply to CRM objects like people, companies, or deals?▼

No. Sharing applies only to data tables, workflows, and agents. Standard CRM objects such as people, companies, deals, and tickets are governed by record-type permissions, not this API.

Why does sharing set remove permissions I did not specify?▼

The set command fully replaces the resource's sharing rows with what you pass. Anything omitted is cleared and workspace falls back to default-open, so always include the complete workspace, users, and teams arrays you want to keep.