Inherited a Realm Recently

The previous coworkers user ID must still be active and not on the Deny list or else all those pipelines would be failing.  I'm also pretty sure that if they own subscriptions and notifications that those will failed to if the old user ID is put on the Deny list.

In the short term, you are going to have to work with your IT department to gain access to the email address used for that user ID so that you can work with the pipelines.  

But the right thing to do in this situation would be to change the old coworkers account to be a Service Account, and then you will have an option to set which users, ie yourself or possibly some other people at the company, to be able to switch to the Service account.

Before changing that account to being a service account, you should go to the old coworkers account and change the name on it and the email address associated with it to something generic like. QuickbaseServiceAccount@mycompany.com.

Obviously, you're going have to work with your IT department or who manages the email system at your company so you have access to that Service Account email account so that you can make the change.

So once you have the old coworkers account configured with a generic name and email address, then you can go into it and set it up as a service account and give yourself access to that account.  

You should be able to go into the Quickbase help system under keyword Service Accounts and get more information, or feel free to post back here if you have other specific questions.

https://help.quickbase.com/docs/setting-up-service-accounts