Typefully Plugin Security
The Typefully plugin is a first-party Navigic integration. It does not load third-party code into Navigic runtime. Typefully-specific API calls and provider error handling are performed by the plugin service, while Navigic control-plane owns workspace installation state, credential storage, operation grants, and audit.
The canonical runtime route is https://plugins.navigic.ai/typefully/....
Navigic should not expose new public per-plugin subdomains for this plugin; the
shared plugin ingress hostname keeps routing, review, and deprecation policy
platform-owned.
Credential Model
- Long-lived Typefully API keys are stored by Navigic control-plane, not by the runtime or model.
- Runtime execution uses short-lived credential leases scoped to one plugin installation and operation.
- Credential leases and API keys must be redacted from logs, dashboard responses, support transcripts, and model-visible tool results.
Permission Model
The drafts:read and drafts:write labels below are Navigic-normalized
permission labels for Typefully plugin operations. Typefully access is API-key
based in managed preview; these labels are not Typefully OAuth scopes.
| Scope | Purpose | Risk |
|---|---|---|
drafts:read | List Typefully drafts and related metadata. | External read |
drafts:write | Create drafts, scheduled posts, or immediate publish requests. | External write |
Write operations require idempotency and should use explicit agent operation grants. Broader Typefully account access should not be granted to an agent unless the workspace owner has reviewed the operation and data-use implications.
Data Boundary
Draft and post content may become model-visible only when a granted agent invokes the relevant Typefully operation. Manual editing, calendar management, and social account administration remain Typefully-owned workflows.
Revocation
To revoke access, disable or delete the Typefully plugin installation in Navigic and rotate or revoke the API key in Typefully settings.