lucidchart-core-workflow-b
Execute Lucidchart secondary workflow: Data-Linked Diagrams. Trigger: "lucidchart data-linked diagrams", "secondary lucidchart workflow".
What this skill does
# Lucidchart — Collaboration & Sharing
## Overview
Invite collaborators, configure permissions, and manage real-time editing sessions on
Lucidchart documents. Use this workflow when you need to share diagrams with teammates,
set granular access controls, track revision history, or manage comments on shared
documents. This is the secondary workflow — for diagram creation and data linking,
see `lucidchart-core-workflow-a`.
## Instructions
### Step 1: Invite Collaborators with Role-Based Permissions
```typescript
const invites = await client.documents.share(doc.documentId, {
recipients: [
{ email: '[email protected]', role: 'editor' },
{ email: '[email protected]', role: 'commenter' },
{ email: '[email protected]', role: 'viewer' },
],
message: 'Please review the updated architecture diagram',
notify: true,
});
invites.forEach(inv =>
console.log(`Invited ${inv.email} as ${inv.role} — status: ${inv.status}`)
);
```
### Step 2: Configure Document-Level Access Controls
```typescript
const permissions = await client.documents.updatePermissions(doc.documentId, {
link_sharing: 'organization', // 'private' | 'organization' | 'anyone_with_link'
allow_download: false,
allow_copy: false,
require_login: true,
expiry: '2026-05-01T00:00:00Z',
});
console.log(`Sharing: ${permissions.link_sharing}, expires: ${permissions.expiry}`);
console.log(`Download: ${permissions.allow_download}, Copy: ${permissions.allow_copy}`);
```
### Step 3: Manage Comments and Review Threads
```typescript
const comments = await client.documents.comments.list(doc.documentId, {
status: 'open',
sort: 'created_desc',
});
comments.items.forEach(c =>
console.log(`[${c.author}] ${c.text} (${c.replies.length} replies)`)
);
// Resolve a comment thread
await client.documents.comments.resolve(doc.documentId, comments.items[0].id, {
resolution_note: 'Updated per feedback — moved DB to separate VPC',
});
```
### Step 4: Track Revision History
```typescript
const revisions = await client.documents.revisions.list(doc.documentId, {
limit: 10,
sort: 'date_desc',
});
revisions.items.forEach(r =>
console.log(`v${r.version} by ${r.author} at ${r.timestamp} — ${r.change_summary}`)
);
await client.documents.revisions.restore(doc.documentId, revisions.items[2].id);
```
## Error Handling
| Issue | Cause | Fix |
|-------|-------|-----|
| `401 Unauthorized` | Invalid or expired OAuth token | Re-authenticate via OAuth2 flow |
| `403 Insufficient permissions` | User lacks edit/share access | Request owner to grant editor role |
| `404 Document not found` | Wrong documentId or document deleted | Verify ID with `client.documents.list()` |
| `409 Conflict` | Concurrent edit collision | Retry — Lucidchart auto-merges most conflicts |
| `422 Invalid email` | Malformed recipient email address | Validate email format before sending invite |
## Output
A successful workflow sends collaboration invites with role-based permissions,
locks down document access with organization-level controls and expiry dates,
and provides a full audit trail of comments, resolutions, and revision history.
## Resources
- [Lucidchart Developer Docs](https://developer.lucid.co/reference/overview)
## Next Steps
See `lucidchart-sdk-patterns` for OAuth configuration and webhook setup.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.