My ideas: Admin Experience

Include security-focused events on audit logs. These could include: user logins/logouts, add IP addresses to all events, MFA success/failure

For clients with a sandbox/trial/developer account where significant effort has gone into testing workflows and integrations in a sandbox environment, migrating to production requires substantial manual work and copy/paste. It would be incredibly ...

Today teammate Groups can be used to grant access to a Workspace with the default access role. This means that if an admin wishes to grant any other role with a teammate Group, they must assign it to users individually. This can becomes messy and ...

Allow shared message templates to be created that can be used across multiple Workspaces. This saves admins from needing to duplicate message templates.

Being able to delegate an inbox to teammates via mobile phone in case we don't have access to the desktop.

Today, teammates have the flexibility to change many preferences and customize their experience. However, in some cases, admins may want to lock the value of some of these preferences in order to create a consistent customer experience and ensure ...

Have a warning banner appear alerting sender from sending a message when emailing an external email domain. Much like this gmail functionality: https://support.google.com/a/answer/7380041?hl=en

Allow admins to" FIELD EDITING: choose who can edit fields on a conversation, teammate, account, contact. If disabled, user cannot edit the field. FIELD DISPLAY: choose which fields apply on objects (contacts, accounts, convo, app objects) bas...

Have the ability to change a once private tag to a shared tag.

If a teammate forgets to mark themselves OOO, then it will disrupt the team's workflows and assignment rules. Today, only a company admin or teammate with 'Teammate - Invite/Manage' permission can change another user's OOO status. By adding a new ...