If the answer here does not fit your case, the docs go considerably deeper.
Create the second key first, deploy it, then revoke the old one. Both work simultaneously, so there is no window where requests fail.
Revoking takes effect within five seconds across every region — there is no grace period.
Exports apply your row-level access rules, dashboards apply the report owner rules. If they differ, the export is the one telling the truth about your permissions.
Yes, provided they use different cursors. Two syncs sharing a cursor will leapfrog each other and both will miss rows.
They keep running under the workspace service identity, and ownership transfers to the workspace admin. Recipients are untouched.
Reports scoped to that person row-level rules will return fewer rows after the transfer. Check them.
Every workspace has a staging environment on the same plan with its own keys and its own data. Break it as often as you like.
Soft-deleted for 30 days so you can undo, then removed from backups within a further 30. After that we genuinely cannot get it back.