Team Access in Wanta
Wanta lets administrators connect work apps and share approved capabilities with team members. Members use the shared capabilities without being given the underlying API keys or tokens.
What determines access?
| Layer | What to check |
|---|---|
| Connected account | Which account is connected, and what the provider permits it to do |
| Connection method | Whether the app uses OAuth, an API key, or another supported method |
| Team permissions | Which members can use the shared capability |
| Subscription | Which permission controls and usage limits are included in the plan |
The Apps catalog lists connection methods and selected actions. An available connection does not grant permissions that the connected account does not have.
When a member leaves
Remove the member from the organization or adjust their access to stop their use of shared capabilities in Wanta. Review any access they hold directly with the external provider separately.
Review changes to external data
Before authorizing a task that sends, edits, or deletes information, check the target account, destination, and requested action. Use the narrowest access appropriate for the task.
See plan details for available permission controls and log retention. For data handling, read the Privacy Policy. For account-specific questions, contact support.