Admin Guides / Access bundles

Change, update and retire a bundle

Change what a live bundle gives, bring the people who hold it up to date, retire it, and how removals and reviews treat bundles.

#Change what a live bundle gives

There are two ways to change a live bundle:

• An administrator edits it in the Admin Workspace. A new entitlement goes to its owner for pre-approval, and new requests include it once approved; the bundle owner is told by email. Taking an entitlement out with Remove from bundle applies to new requests straight away, and the row stays as history.
• Anyone proposes a change with the Onboard an Access Bundle form. See Propose a bundle.

Each change raises the bundle's version. New requests get the bundle as it is now; people who already hold it keep what they have until you update them.

#Bring holders up to date

People who hold an older version are shown as behind, and the bundle owner is emailed once per version with how many people that is. When the owner is not a Warde administrator, the administrators who review bundles are told too, because only an administrator can update holders.

Select Update people who have it on the bundle to bring them onto the current version. Warde works out, for each holder, what the bundle now gives that they lack and what they hold through it that it no longer gives, and raises one request per holder on the hidden Access bundle updated item. That request asks nobody, because the change was the decision: engine work goes to the queue and manual work becomes a task under the holder's request. Their holding moves to the new version once every line has completed. A large bundle is updated in the background, 25 holders at a time.

A change proposed with the Onboard an Access Bundle form can update holders as part of the same request, and its approvers are told what approving does to those people.

To find people who are behind before you update them, or to have their managers confirm they still need it, run an access review of bundle holdings with Only holders behind the current version ticked. See Define a campaign.

#Retire a bundle

Select Retire on the bundle. A retired bundle can no longer be requested or granted, and it is closed for good. To take it away from the people who hold it, remove it from them, or review it.

Lifecycle integrations find bundles by name, so check your joiner process before you retire or rename a birthright bundle.

#How removal treats bundles

• People remove a bundle whole, with the Remove Access Bundles form or Remove beside it on My Access. See Remove a bundle in the user guide.
• A single entitlement that came in a bundle cannot be removed on its own; Warde tells the person to remove the bundle instead.
• A birthright bundle cannot be removed by a request, because the next lifecycle call would grant it again. Change the rule or the HR details that give it.
• Removing a bundle removes every entitlement it gave the person, except anything they also hold some other way.

#How reviews treat bundles

See Access review campaigns.