Temporary Group Assignments

Why should you use Temporary Group Assignments?

Some examples may be:

A user needs temporary role elevation in a tool that’s managed by an Okta group.

A user needs access to an application for a time boxed project and will no longer need access to it afterwards.

A user needs to temporarily bypass authentication restrictions. For example, at Coda we restrict employee Okta logins to your home country. That restriction can be bypassed via a group if you are traveling internationally.

Instructions

Admin adds a row on the table below and selects the Okta User and “Okta Group.”

Admin chooses the time frame for which the user should be in the group.

The Add and Remove buttons are set to be disabled if either of the below conditions are true.

Today’s date does not match the From or Until columns.

The Add Result or Remove Result have a successful HTTP response code. (These columns automatically update with the HTTP response code when the pack attempts to take the action specified with the Okta API.)

You can then create Automations in your doc to “press” these buttons at a scheduled time (for example every day at 12AM) so that scheduled additions and removals happen without you needing to physically press the button.

Temporary Group Assignments

Temporary Group Assignments

Okta User

Okta Groups

From

Until

Add

Remove

khoi@coda.io

Coda Dev Admins

11/2/2023

8/5/2022

Add

Remove

oleg@coda.io

Origin Country Bypass

7/28/2022

8/31/2022

Add

Remove

testing12345@atko.com

Groups-Team

7/27/2022

10/7/2022

Add

Remove

There are no rows in this table

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.