Resource guest access

Hello, Yes, this can be achieved by creating two separate ZTNA resources with different external FQDNs pointing to the same internal IP/FQDN and different user groups assigned to each of the resources. 

Ok, but if the resource is an external SaaS?

The current concept of gating access to Saas applications like Salesforce or Dropbox is possible via an agent based approach only. It involves using an agent to route traffic to the gateway and whitelisting the WAN IP of the gateway in the Saas application. This would not be possible in the agent less approach.

The current concept of gating access to Saas applications like Salesforce or Dropbox is possible via an agent based approach only. It involves using an agent to route traffic to the gateway and whitelisting the WAN IP of the gateway in the Saas application. This would not be possible in the agent less approach.