Rippling
See everyone Rippling knows about - employees and leavers with their status, start and end dates, department, manager and work email - plus Rippling user accounts, groups, the third-party app accounts Rippling creates and suspends for each person, Rippling-managed devices and the software pushed to them, and the Rippling Activity Log. No pay, date of birth, address or government id is ever collected.
Questions you can answer 18
Each one is a saved query that ships with ConfigView, reading your Rippling data on your own server. Ask it in plain English, SQL, Slack or the API.
- Which apps has Rippling provisioned for each person?
- What apps does this employee have access to through Rippling?
- Who has the most app accounts provisioned by Rippling?
- Which app accounts can Rippling not match to an employee?
- Are there shared or contractor accounts in apps Rippling manages?
- Which accounts will Rippling never offboard?
- Which Rippling-managed laptops are unencrypted or not checking in?
- Is any leaver still assigned a device in Rippling?
- Which devices in Rippling have not checked in for 30 days?
- Which leavers in Rippling still have active accounts?
- Who was terminated in Rippling but is still active in Okta or Google?
- Did offboarding in Rippling miss any app accounts?
- Where did Rippling app provisioning fail?
- Did Rippling fail to suspend any leaver accounts?
- Which Rippling app invites or suspensions are stuck?
- Has anyone signed in to Rippling from a new country?
- Show unusual Rippling sign-in locations this month
- Were there failed Rippling sign-ins from abroad?
No Rippling questions match that yet. Try a shorter word.
What ConfigView collects from Rippling 11
-
Activity log
Rippling's Activity Log: sign-ins, admin changes, app provisioning, device actions and other events with who did it, what it touched, the outcome, and the IP address and country it came from. Kept beyond Rippling's 90 days.
-
App accounts
Every account Rippling has created, matched or suspended in a connected third-party app (Slack, Google, GitHub and so on): which app, which person, the account's email or username there, and its provisioning state.
-
Company
The Rippling company the token belongs to: its name, legal name and trading name, and how many legal entities it has.
-
Departments
Departments and the department each one sits under, for grouping people by team.
-
Devices
Laptops, desktops, phones and tablets managed by Rippling IT: serial, model, OS, who it is assigned to, MDM enrollment, disk encryption and last check-in.
-
Software deployments
Software Rippling IT pushes to company devices: the app, its category, which platforms, and whether it targets a group of people or a group of devices.
-
Group members
Who is in each visible Rippling group, by worker, name and work email.
-
Groups
Rippling groups (supergroups) used to decide who gets which app, policy and permission: name, type, the app that owns it, and whether it includes terminated people or non-employees.
-
Teams
Teams defined in Rippling and the team each one belongs to.
-
User accounts
Rippling login accounts: username, work email, and whether the account can still sign in to Rippling and the apps it grants.
-
Workers
Everyone who works or has worked at the company: employment status, start and end dates, title, department, manager and work email. No pay, date of birth, address or government id is collected.