Infrastructure

OutThink

Ploy connects to OutThink's API to show who holds an OutThink learner seat and who can administer OutThink in Command Center, and to invite, change and remove Command Center admins from Ploy.

This integration is in beta. It was built from OutThink's published API documentation and has not yet run against a live OutThink tenant. During setup you are asked to agree to Ploy capturing redacted error data: if OutThink returns an error to Ploy, Ploy keeps the error with names, emails and other personal values removed, so we can fix the integration quickly. Nothing is captured when calls succeed.

What Ploy reads

  • Learners: every active learner in your OutThink tenant, across all of its organisations. Each one shows as having access to OutThink.

  • Command Center admins and instructors: every admin and instructor, with their role and when they were last active. They show as having access to the OutThink Command Center resource, with their role (Admin or Instructor) as the entitlement. Someone who has been invited but has not signed in yet shows as pending.

Ploy does not read training results, phishing simulation results or risk scores. OutThink reports whether it requires multi-factor authentication for an admin but not whether they have set it up, so Ploy does not show multi-factor status for OutThink.

What Ploy can change

  • Invite a Command Center admin or instructor by email, with a role (Instructor if none is given) and optionally an organisation.

  • Change a Command Center user between the Admin and Instructor roles.

  • Remove a Command Center admin or instructor.

Learners are managed by your identity provider, which provisions them into OutThink through SCIM. Ploy does not add, disable or remove learners. To remove a learner, remove them in your identity provider; Ploy shows the change after its next scan.

Before you start

You need to be an OutThink Command Center administrator who can create API keys.

Steps

  1. In Ploy, open Integrations, find OutThink and click Connect. Tick the beta consent checkbox.

  2. Choose your data-hosting region: Europe (and everywhere else), United States, or Canada. If you are not sure, ask your OutThink account manager.

  3. In OutThink Command Center, open Settings, then API. Copy the Customer ID shown on that page and paste it into Ploy.

  4. On the same page, create a new API key. Give it permission to read users and to manage admin users. Copy the key straight away: OutThink shows it only once. Paste it into Ploy.

  5. Click Test connection, then Save.

Things to know

  • API keys expire after one year. Set a reminder to create a new key and update the connection in Ploy before it expires.

  • The API key can see your whole OutThink tenant, including every organisation and sub-organisation in it.

  • A learner who is disabled in OutThink stops showing as having access after the next scan, not immediately.

  • Learners are scanned every six hours and admins every hour.

Troubleshooting

  • "OutThink rejected that API key": the key was not copied in full, was revoked, or has expired. Create a new key and paste it again.

  • "refused to list your learners": the key does not have permission to read users. Edit the key's permissions in Settings, API.

  • "OutThink refused the change" on an invite, role change or removal: the key does not have permission to manage admin users.

Was this helpful?
Was this helpful?