# HiBob to Okta new hire activation script tool

Each morning it finds who starts today in HiBob, puts their title, department and manager on their staged Okta account and activates it, then opens one ticket for anyone it couldn't set up.

[Book a demo](/demo) · [See the library](/library)

## More like this

- [Rippling new hire onboarding automation](/library/automations/rippling-new-hire-onboarding)
- [Okta group access request runbook](/library/runbooks/okta-group-access-request)
- [How script tools work](/product/script-tools)
- [The full library](/library)

## Frequently asked questions

### What does the HiBob to Okta new hire activation script tool need?

A HiBob service user and an Okta API token, saved as write-only secrets. The service user needs to see the Root and Work categories, and people who haven't started yet: HiBob keeps new hires inactive until their first day. Each new hire needs a staged Okta account whose login is their HiBob work email. Replace acme.okta.com in the code with your Okta domain.

### How do I run the HiBob to Okta new hire activation script tool every morning?

Call it from an automation on a daily schedule. It works out today's date itself, and Okta's activation email stays off unless you turn it on, for teams that hand over credentials on day one. Activating accounts changes Okta, so each run waits for one approval. Anyone with no Okta account, or an account that isn't staged, goes on a single ticket, and the rest of the day's hires are still set up.

### Is the HiBob to Okta new hire activation script tool one of Risotto's templates?

No. We wrote it for this library from what script tools can do today. Ask Risotto's Assistant for a script tool like it, and it writes one for your HiBob and Okta.

Source: https://www.tryrisotto.com/library/script-tools/hibob-okta-new-hire-activation
