You connect OpenText Secure Cloud once per MSP, with an API credential and a refresh token from Secure Cloud. Every agent you enable can then use it, with permissions you control per agent.
What Neo can do with OpenText Secure Cloud
Customers & Users
Read your Secure Cloud customers and their users. Create a user, change a user’s details, and add, change or remove a user’s services and Microsoft 365 licences. Giving a user a role uses Admins & Roles.
Subscriptions & Charges
Read each customer’s subscriptions with their seat counts, terms and renewal dates, and search charges and charge events. Read only.
Orders & Trials
Read Webroot licences and their order status, place an order and start a trial. Cancelling a product always waits on a technician.
Webroot Endpoints
Read sites, endpoints, groups, policies and threat history. Scan, clean up, restart or isolate named endpoints, move them between groups and apply a policy. Changing an endpoint’s keycode always waits on a technician.
DNS Protection
Read DNS Protection policies, blocked traffic and traffic summaries, and change a site’s policy mappings.
Status & Reports
Read endpoint agent status, console and site statistics, and the usage reports per console, site and customer. Read only.
Neo cannot change a subscription’s seat quantity in OpenText Secure Cloud. When a ticket needs more or fewer seats, the agent gives the technician the subscription, its current quantity and the quantity needed, and the technician changes it in Secure Cloud.
Your clients are mapped automatically
Neo matches your Secure Cloud customers to the companies in your PSA. The mapping is on the OpenText Secure Cloud card’s Organization Mapping tab. Neo refreshes it after each PSA sync and when you save the credentials. It reads active customers only. Neo tries an exact name match first, then a match after it removes a legal-form suffix (Ltd, Inc, LLC). Then it compares the customer’s website with your companies’ domains, and an AI match covers the names the first steps miss. Your agents get a unique exact-name match, or a match you confirm, directly. The agent then works in the ticket’s client without searching for it. Every other match is only a suggestion: a match after a suffix is removed, a name two of your companies share, two customers matched to one company, a website match and an AI match. It stays on the Organization Mapping tab until someone confirms it. You can set a mapping by hand on the same tab, and it survives every later sync.Why connect OpenText Secure Cloud
- New starters get their licence from the ticket. The agent reads which services and licences the client can assign, creates the user with the Microsoft 365 licence, and reads the user back to confirm it.
- Leavers lose their licence the same way. The agent removes the service or the licence from the user and reports what the user holds afterwards.
- Billing questions get an answer from the source. The agent reads the client’s subscriptions, seat counts, terms and charges, and when the seat count last changed.
- You decide how far agents go on their own. Each area has its own approval setting. Only admin and role changes, changing an endpoint’s keycode, uninstalling or deactivating Webroot on endpoints, suspending or deactivating a site, and cancelling a product always wait on a technician. The OpenText Secure Cloud API tool reference lists the controls.
How agents reach OpenText Secure Cloud
When you enable any OpenText Secure Cloud permission group on an agent, Neo adds the Vendor API tool to that agent’s toolbox. There is nothing to install. The agent uses the credentials you saved in the dashboard, and every call stays inside the areas and access levels you allowed.Where to go next
Connecting OpenText Secure Cloud to Neo
Setup steps for the API credential and refresh token, per-agent access levels, and the safety controls that stay in place.