Who is this for?
- Partner leadership users who only use Slack to communicate with Grubhub members and do not log in to Okta, Zendesk, Five9, or any other Grubhub application.
Why are we doing this?
- Housekeeping inactive Okta accounts. Okta requires a license, if an account has not been logged into in over 30 days, that license is disabled. This then prompts a user to attempt to reset their password, essentially needing the Okta account to be re-enabled. Without needing the Okta SSO to access Slack, leaders can avoid this issue.
How does this work?
- A Slack invitation will be sent directly to the users @company.com with instructions on how to log in to Slack without needing to utilize SSO from Okta.
What do we need?
- A list of users’ Name and Company Email who this is applicable for.
- Fill out the form here: Asana form
- ACTION REQUIRED: Any user shared needs to be terminated via the SFTP upload and then completely removed from the SFTP file once the termination has been successful.
- Find the email address in the SFTP file
- Update the “Employee Status” field to “Inactive”
- Update the “Termination Date” field to the current day, in the MM-DD-YYYY format
- Allow one day for successful upload.
- After the employee status has been successfully updated, completely remove the user from the SFTP upload.
- THIS IS ONLY ACCEPTABLE IN THIS SPECIFIC SCENARIO; USERS SHOULD NEVER BE REMOVED FROM THE SFTP UPLOAD UNLESS DIRECTED TO DO SO BY GRUBHUB!
- Once this SFTP update has been successfully uploaded, Grubhub will remove the previous Okta account entirely and send a Slack invitation to the user.
*After an email address has been terminated, their username will be disabled. They CAN NOT log in with their @grubhub.com email address.