1. Overview
The Monday.com integration reads workspaces, boards, item pages, updates, users, teams, and configured relationships through a workspace-managed API token.
Optional workspace and board IDs narrow the population; Seedling uses a pinned API version and does not expose Monday.com mutations.
2. Connection and scope
Seedling verifies the provider account before storing the workspace connection. A current Seedling workspace administrator controls installation and disconnect; account identity is never inferred from an email address or display name.
- Monday.com API token
- The current personal API token inherits a dedicated account's native access, including visible private boards. OAuth is a future mode only.
- Connection ownership
- This connector is workspace-only. A current Seedling workspace administrator controls installation, credential replacement, disconnect, and purge for the exact connection.
3. Monday.com data Seedling accesses
Seedling uses synchronized information for source-backed search, operating context, verification, and customer-approved workflows. Availability depends on the connected account, selected resources, provider plan, and native permissions.
- Work structure
- Workspaces, boards, groups, columns, statuses, teams, and configured fields.
- Items
- Items, subitems, owners, dates, dependencies, values, and relationships.
- Collaboration
- Updates, replies, users, teams, and available board activity context.
4. Read-only permission contract
The current token is bounded by its owner; the documented future OAuth ceiling remains read-only.
- boards:read — boards, groups, columns, items, subitems, and values.
- updates:read — item and board updates and replies.
- users:read and teams:read — attribution and team context.
- workspaces:read — workspace identity and board organization.
- No board, item, update, user, team, or workspace write scope is requested.
5. Security and access
- Provider credentials and other connection secrets are encrypted in the workspace tenant data plane, never returned to the browser, and excluded from logs and queue payloads.
- Every source, synchronization, secret lookup, audience contribution, disconnect, and purge remains bound to the exact connection that created it.
- The provider does not expose enough complete object-level audience evidence for Seedling to reproduce native permissions safely. Workspace content therefore uses the connection's restricted-by-default workspace-or-no-human-access policy; administrator and steward status grant no raw-content bypass.
- Generated output cannot bypass Seedling's human review, verification, and approval gates.
6. Retention and deletion
- Connected data
- Synchronized Monday.com records remain while the connection is active and are removed through a durable integration purge after disconnect.
- Credentials
- Stored Monday.com credentials or connection secrets and connection-owned synchronization state are deleted from active Seedling systems as part of the purge.
- Backups
- Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion.