Permissions and troubleshooting
Account authorization
Each MCP authorization operates as an individual Landit user. Tools should see that user’s accessible resources and perform mutations under that account.
MCPReview the account boundary
Confirm the Landit identity during OAuth authorization. Workspace-shared templates and assets can be accessible, while user variables and prompt definitions remain owner-specific. Authorizing one account does not give a teammate’s personal definitions to another.
Understand actions
Read tools list or inspect existing records. enrich_prospects starts new Page generation work. update_asset_sharing changes workspace visibility. Use your assistant client’s approval controls and inspect the tool arguments before allowing consequential actions.
Explicit template selection is required for creation. Tool availability is not permission for the assistant to choose a template or create Pages outside your request.
Revoke and reconnect
Disconnect the app in your assistant client when it is no longer needed. Review Landit’s authorized-application controls where available and confirm revocation by testing a read. Removing the client configuration and revoking a grant are different checkpoints.
Revocation does not delete Pages, assets, or CRM updates already created. Existing public links need their own lifecycle review. Verify token refresh and revocation in your specific client when those controls matter to your workflow.
Never paste tokens, passwords, or API keys into chat. Follow the browser authorization flow instead.