RahalCorporate
DelegationAdmin Guide

Revoking Delegations

How to permanently remove delegation access

Revoking Delegations

Revoking a delegation permanently removes the delegate's access to the delegator's travelers. This action cannot be undone.

When to Revoke

Common reasons to revoke a delegation:

SituationAction
Employee leaves the companyRevoke all their delegations
Role changeRevoke if delegation no longer needed
Security concernRevoke immediately
Relationship endedRevoke when no longer needed
Temporary need fulfilledRevoke after completion

Consider deactivating instead of revoking if there's a chance the delegation will be needed again. Deactivated delegations can be reactivated; revoked delegations must be recreated.

Revoking vs Deactivating

ActionEffectReversible
DeactivateSuspends access temporarilyYes - reactivate anytime
RevokePermanently removes the delegationNo - must recreate

Choose Deactivate when:

  • Temporary suspension needed
  • May need to restore access later
  • Testing access removal

Choose Revoke when:

  • Delegation is no longer needed
  • User has left the organization
  • Security/compliance requirement

Revoke a Delegation

Find the Delegation

  1. Navigate to Delegations in the dashboard
  2. Use search or filters to find the delegation
  3. Identify the correct row by delegate and delegator names

Initiate Revocation

  1. Click the trash icon in the Actions column
  2. A confirmation dialog appears

Confirm Revocation

The dialog shows:

  • Delegate name (who loses access)
  • Delegator name (whose travelers become inaccessible)

Review the information, then click Confirm to proceed.

Verify Removal

  1. The delegation disappears from the table
  2. A success toast confirms the revocation
  3. The delegate can no longer access the delegator's travelers

Confirmation Dialog

The confirmation dialog displays a warning with the names of both users involved:

Revoke confirmation dialog showing the delegate and delegator names

This helps prevent accidental revocations by confirming both parties.

What Happens After Revocation

Immediate Effects

  1. Access removed: Delegate cannot access delegator's travelers
  2. API blocked: Any API calls using delegation context will fail
  3. UI updated: Delegator's travelers no longer appear for delegate

Ongoing Bookings

If the delegate has an ongoing booking flow:

  • Search results remain visible (cached)
  • Selecting travelers may fail
  • Booking submission will fail with error
  • Error: "Your access to book for [name] has been revoked"

Existing Bookings

Bookings created before revocation are unaffected:

  • Booking records remain intact
  • Historical data preserved
  • Attribution to delegator unchanged

Bulk Revocation

When a user leaves the organization, revoke all their delegations:

Revoking All Delegations FROM a User

When someone who granted access leaves:

  1. Search for the delegator's name/email
  2. Revoke each delegation where they are the "Grants Access" user
  3. This removes all delegates' access to their travelers

Revoking All Delegations TO a User

When someone who received access leaves:

  1. Search for the delegate's name/email
  2. Revoke each delegation where they are the "Receives Access" user
  3. This removes their access to all delegators' travelers

There's no single-click "revoke all" button. Each delegation must be revoked individually to ensure intentionality.

Employee Offboarding

Recommended steps when an employee leaves:

Identify Delegations

  1. Search for the departing employee's name
  2. Note all delegations where they appear as delegate or delegator

Revoke Delegator Relationships

If they granted access to others:

  1. Find delegations where they are "Grants Access"
  2. Revoke each delegation
  3. Their travelers become inaccessible to former delegates

Revoke Delegate Relationships

If they received access from others:

  1. Find delegations where they are "Receives Access"
  2. Revoke each delegation
  3. They lose access to all delegators' travelers

Document

Record the revocations for compliance purposes.

Accidental Revocation

If you accidentally revoke a delegation:

  1. The delegation cannot be restored
  2. You must create a new delegation
  3. Use the same configuration as before
  4. The new delegation will have a different ID and creation date

To avoid accidental revocations:

  • Use the confirmation dialog carefully
  • Consider deactivating first if unsure
  • Double-check delegate and delegator names

Audit Trail

Revocation events are logged with:

FieldValue
Event Typedelegation.revoked
Delegation IDThe revoked delegation's ID
DelegateUser who lost access
DelegatorUser whose travelers were affected
Revoked ByAdministrator who performed the action
TimestampWhen the revocation occurred

Managing Delegations

How to update and maintain delegation relationships

Troubleshooting

Common delegation issues and how to resolve them

On this page

Revoking DelegationsWhen to RevokeRevoking vs DeactivatingRevoke a DelegationFind the DelegationInitiate RevocationConfirm RevocationVerify RemovalConfirmation DialogWhat Happens After RevocationImmediate EffectsOngoing BookingsExisting BookingsBulk RevocationRevoking All Delegations FROM a UserRevoking All Delegations TO a UserEmployee OffboardingIdentify DelegationsRevoke Delegator RelationshipsRevoke Delegate RelationshipsDocumentAccidental RevocationAudit TrailRelated Topics