Qualtrics
See who can administer your Qualtrics brand, who holds a Qualtrics account but hasn't logged in for 90 days, which accounts still belong to people who have left, who may call the Qualtrics API, where event subscriptions push survey events outside the company, and the brand's sign-in and permission-change history - never surveys, questions or responses.
Questions you can answer 15
Each one is a saved query that ships with ConfigView, reading your Qualtrics data on your own server. Ask it in plain English, SQL, Slack or the API.
- Do any leavers still have active Qualtrics accounts?
- Which offboarded people can still log in to Qualtrics?
- Who can use the Qualtrics API?
- Which Qualtrics users can generate an API token?
- Who are the Qualtrics brand admins?
- Who can administer Qualtrics?
- Which Qualtrics admins have not logged in recently?
- Where does Qualtrics send survey responses?
- Which Qualtrics webhooks go to outside hosts?
- Is Qualtrics pushing responses to Zapier or other third parties?
- Which Qualtrics users haven't logged in for 90 days?
- Are we paying for Qualtrics accounts nobody uses?
- Which Qualtrics accounts could be disabled before renewal?
- Who was made a Qualtrics brand admin recently?
- What Qualtrics permission changes happened in the last 30 days?
No Qualtrics questions match that yet. Try a shorter word.
What ConfigView collects from Qualtrics 8
-
Activity Log
The brand's activity log: sign-ins (successful, failed, proxy and single sign-on, with IP, location, browser and second factor), accounts created, changed or deleted, user-type and permission changes, role membership and role permission changes, and brand setting changes. Kept as a permanent ledger.
-
Divisions
Each division the brand's users and groups belong to: name, status (active or disabled), when and by whom it was created, response counts, how many users it holds, and the permissions set at division level.
-
Event Subscriptions (webhooks)
Event subscriptions - the webhooks that push Qualtrics events such as completed survey responses out to another system: destination host (never the full URL), whether it is plain http, which events, whether the payload is encrypted, and how many deliveries succeeded.
-
Group Members
Who is in each Qualtrics group, with each member's username, email, user type and account status, so group access can be reviewed person by person.
-
Groups
User groups in the brand - the way Qualtrics shares surveys, libraries and dashboards with many people at once: name, type, division, whether membership is automatic, and who created it when.
-
Organization (brand)
The Qualtrics brand itself: name, type, status, license expiry date, survey and response counts, and how many users logged in within the last 1, 7, 30, 90 and 120 days or never - plus which account ConfigView is connected as.
-
User Details (last login)
Per-user detail for every account: last login, account created and expiry dates, password last changed, sign-in identity provider, response counts, and the permissions switched on - including whether the user may call the Qualtrics API. Refreshed a slice per run, stalest first.
-
Users
Every Qualtrics account in the brand, including disabled ones: username, email, name, user type (Brand Administrator, licensed user, participant and custom types), division and account status.