Overview
'Salesforce Integration Only' restricts selected users to accessing SendSafely through the SendSafely Salesforce app. Restricted users can send, receive, view, and download SendSafely files from Salesforce as usual. They cannot use the SendSafely web portal, the SendSafely API, or any other SendSafely integration.
Admins apply the restriction by adding users to a Security Group that has the Salesforce Integration Only permission enabled. Contact support@sendafely.com to configure a security group to enable this feature.
Availability
Availability: Salesforce Integration Only is available for Business and Enterprise plans.
Requirements:
- The SendSafely Salesforce app must be installed and configured for your Salesforce org. See the SendSafely Salesforce Integration Setup Checklist.
- Restricted users need a registered SendSafely account in your organization.
- Restricted users are managed through a Security Group with the Salesforce Integration Only permission.
What Restricted Users Can Access
Registration, login, password reset and the Salesforce app are the only places a restricted user can use SendSafely. All other authenticated access is blocked.
| Access point | Restricted user |
|---|---|
| SendSafely Salesforce app (send, receive, view, download) | Allowed |
| Web portal login page | Allowed |
| Account registration and password reset pages | Allowed |
| All other web portal pages (Send, Workspaces, Personal URL, etc.) | Blocked |
| SendSafely API (direct API calls) | Blocked |
| Other integrations (Outlook, Gmail, Zendesk, Freshdesk, Slack, and others) | Blocked |
Restricted users can sign in with any login method your organization supports: Salesforce OAuth, username and password, SAML SSO, or Google. They are not prompted to create a Trusted Browser key when they sign in.
Enabling Salesforce Integration Only
- Contact support@sendsafely.com to request a Security Group with the Salesforce Integration Only permission. SendSafely Support creates and names the group for your organization.
- In the Enterprise Console, open the Security Group.
- Add the users you want to restrict. You can add users one at a time or in bulk, up to 50 at a time as a comma-separated list.
The restriction takes effect for each user as soon as they are added to the group. You can also manage group membership through the SendSafely API.
Tip: Test with one user before you add a full team. Confirm they can sign in, send, and download from Salesforce, and that they are blocked from the web portal.
Removing the Restriction
To give a user full access again, remove them from the Security Group in the Enterprise Console. The user can then use the web portal, the API, and other integrations as normal, subject to your organization's other settings.
What Restricted Users See When Blocked
Web portal: If a restricted user opens any web portal page other than login, registration, or password reset, they see an access denied page titled "This account is configured for integration-only access." The page tells them to use SendSafely within their integrated application and to contact their SendSafely administrator if they believe this is an error.
API and other integrations: If a restricted user calls the API directly or signs in to another SendSafely integration, the request fails with this error: "Your account is configured for integration-only access. Access to this feature is not available."
Frequently Asked Questions
Does this affect recipients of packages sent by restricted users? No. The restriction applies only to the restricted user's own account. Recipients open secure links as usual.
Can I restrict every user in my organization? Yes. Contact support@sendsafely.com to apply the restriction across your whole organization instead of through a Security Group.
Is this available for other integrations, such as Zendesk? Not yet, but Zendesk Integration only is coming soon.
Does this require SSO or SCIM? No. Salesforce Integration Only works for any user, however they were provisioned and however they sign in.
Comments
0 comments
Article is closed for comments.