Preset Feature Feedback
What is the problem or goal you're trying to solve or accomplish?
When a user attempts to access a Preset workspace they don't have permission to, they see a generic access-denied message with no actionable guidance. The user doesn't know who to contact, what access to request, or what steps to follow. This generates unnecessary support tickets and creates a poor user experience, especially in enterprise environments with established access request workflows (SCIM/Okta, Freshservice catalogs, etc.).
How are you solving it currently?
There is no current workaround within Preset. Customers rely on external documentation, onboarding materials, or manual communication to tell users what to do if they're denied access, but none of that is surfaced at the moment the error occurs. Users typically end up contacting their IT helpdesk or the Preset workspace admin directly, creating avoidable support overhead.
What is your recommended solution?
Provide a workspace-level setting in Preset Manager that allows Workspace Admins to configure a custom message and/or URL displayed on the access-denied page. This could include a free-text message field (e.g., "To request access, submit a ticket via [internal portal]") and an optional link/button pointing to an external resource (e.g., a Freshservice catalog item or internal wiki). If no custom message is configured, the default generic error would remain as a fallback.
