How can workspace access be restricted to specific IP addresses?
amaise can restrict access to a workspace to a defined list of IP addresses (IP-Allowlist). When filtering is active, only the listed IPv4 and IPv6 addresses and CIDR ranges reach the workspace — all other access is rejected at the authentication layer.
Key features:
Covers the web app and the API: The restriction applies to the web app, the API and the live connection the web app uses for real-time updates — not just the API.
Public share links are outside it: A shared export stays reachable for its recipients from any network. Share links are deliberately outside the restriction, because they exist for work with companies outside your own network.
Agent integrations are only partly covered: The SDK sends most calls without naming a workspace up front, so amaise resolves the workspace from the case afterwards — past the point where the address is checked. Treat the allow list as a control on people's access, not as the only control on an integration's credentials.
The public IP is what counts: The public IP address (egress IP) as amaise sees it is checked — not the local address of the device.
Configured by administrators: The list is maintained by administrators under «Settings» → «Security».
Recovery: amaise Support retains access for recovery cases, should an organization accidentally lock itself out.