Allow for Contact and Contact List Restriction for IdP-Managed Teammate Groups via the API
If a teammate group's membership is managed by an IdP (Entra, Okta, etc.), the teammate group cannot be edited in Front via the API. This behavior prevents Admin from controlling a teammate group's contacts and contact list access. To control the ...
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 ...
Show inbox visibility settings when creating a new tag during rule creation
The majority of our company's tags are only visible to specific inboxes. If a new tag is added during rule creation it is automatically made visible to all inboxes which adds a manual, often forgotten step of editing the tag after it's been created.
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...
If a teammate is invited without specifying a workspace to add the teammate to (generally via SCIM), Front will add them to the "default" workspace, which is the workspace with the lowest ID. This can lead to teammates being added to a workspace t...
More historical data fields (Last Used, Last Modified, Created By, etc)
We have a pretty big buildout and user base in Front. It is difficult to understand the relevance, history, and ownership of key configuration items such as Tags, Message Templates, Signatures, and Rules. These objects accumulate and change over t...
Long threads get refreshed and can’t find the old chat and plan. Especially if it something that is more complex and that might take a while to actually execute the plan.