Reconnect and revoke access

Identify the layer

A provider connection authorizes Ridian to access a calendar service. An assistant grant authorizes a particular client to use a subset of that access. Your Ridian login is a third, separate session. Repeating the wrong login may not fix the error.

Renew the existing provider account

Open the affected connection and choose reconnect. Use the same provider identity and confirm the needed consent. For CalDAV, replace an expired app-specific password through the existing connection. Check the provider preset and username so you do not accidentally create a duplicate account.

After reconnecting, verify account status, accessible calendars and whether the original test calendar still has the expected read/write rights. Missing Microsoft permissions can reflect partial consent; a successful return to Ridian alone does not prove that every requested scope was granted.

Refresh a client

If the provider is healthy but a client cannot see a newly allowed tool, refresh the connector’s tool list where supported. If necessary, remove and re-add that connector and start a new conversation. Review permissions again. This can address stale tool metadata, but it does not fix a genuine server-side permission denial.

Revoke deliberately

Revoke a client’s access to stop that client. Disconnect the calendar account only if you intend to stop the provider connection and the dependent workflows. Neither action should be used as an instruction to delete unrelated events at the provider.