Skip to main content

Admin controls and managing Every Agent resources

Which resources users and workspace administrators can manage themselves, and when the Every team needs to help.

The actions available to you depend on who owns the resource and whether it is personal or shared across the workspace.

What can users manage themselves?

Users can manage, edit, or remove:

  • Their own connections

  • Resources they own

This includes making changes to personal resources without affecting resources owned by other people.

What can workspace administrators manage?

Workspace administrators see the full workspace list on the Connections, Skills, and Automations pages of the Every dashboard, and can manage shared workspace resources from there.

Admin > Settings holds workspace-wide controls:

  • Slack: the connected Slack workspace and the Every team it is linked to

  • Channels: every channel Every Agent is in, and whether it replies to every message in each one

  • Logs: an audit log of tasks, skills, connections, and connection use, searchable by item or person and filterable by type and date

Administrators can also access and edit individual users' resources, including automations and skills, when an administrative correction is required. An administrator can pause an automation that is posting in a channel, even one owned by someone else, and the reason is recorded.

The Users page is where administrators add people to the workspace's Every team plan.

Can administrators limit who uses Every Agent?

Not currently. There's no setting to limit Every Agent or the Every dashboard to specific people. Anyone in a channel where Every Agent has been added can work with it, and anyone with a free Every account can use the dashboard.

Can an administrator correct inaccurate company-wide guidance?

Yes. An administrator can correct an inaccurate directive directly.

Which requests require help from the Every team?

Start a chat from the Messenger or email [email protected] for help with:

  • Whole-workspace deletion

  • Account closure

  • Retention exceptions

  • Requests involving resources owned by someone else

Include the workspace, affected user or resource, and the scope of the request. The Every team will confirm the scope before completing changes that could affect other people or an entire workspace.

Did this answer your question?