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 ...
Admins need to grant Workspace admins permission to edit teammate settings, manage access and invite new teammates to Front, so that their team can work autonomously. However, giving them this permission also grants them the ability to add new lic...
Add a new permission for managing shifts that can be added inside a custom role. This enables teammates other than full Workspace admins to manage shifts.
Restrict conversation actions for a specific inbox i.e. View-only inbox access
Today, teammates can be given different sets of conversation permissions (e.g. ability to send a reply) between different Workspaces. However, creating a dedicated Workspace just for this purpose can be over-the-top and have undesired side effects...
Limit who can add, edit and delete contacts and accounts. This could also include limitations on freely browsing through contact data in the contact manager, although, we cannot restrict the ability to view contact data entirely.
Frontline users can see rule logic with view-only access
This will help with transparency as to how/why messages are getting assigned to them or not. This could be managed with a view-only permission for custom roles.
Hi! I'd like to be able to restrict moving messages between workspaces. For example, I have an IT workspace that I'd rather users in my Production workspace not be able to move things to. There may also be inboxes in a workspace that people should...
Split billing permissions from Company admin status
Today, company admin is the highest level of access which allows the user to access anything in Front, including billing actions such as adding licenses, changing payment details or upgrading plans. We could introduce a new notion of billing permi...