Give every person their own named login for each GC portal, keep those credentials in a company password manager, and tie multi-factor authentication to the person through an authenticator app on a company-managed device, not a personal phone. When someone leaves, remove their access to every portal the same hour. Rudick Innovation & Technology provides construction IT support that covers the office and the field, including portal access.
If your team already juggles more portal logins than anyone can list from memory, we can help you sort them out. Book an Appointment.
Why do GC portal logins become a problem?
Every general contractor and owner picks its own platform. A subcontractor working for six GCs might submit pay apps through Textura for one, GCPay for another, and Procore for three more, then check drawings in a separate plan room and upload certificates of insurance to a prequalification portal. Each one needs its own login.
Most companies never plan for this. Logins get created by whoever happened to be on the first project, often with a personal email address or a shared one like ap@ or estimating@. The password lands in a spreadsheet or a text thread. When a portal turns on multi-factor authentication, the codes go to the phone of the person who set it up.
Then that person goes on vacation, changes roles, or quits. A pay app is due Friday and nobody can sign in, or, worse, a former employee still can.
What goes wrong with shared logins?
Shared logins feel efficient until something goes wrong. They cause four problems:
- No accountability. When five people use one account, the portal cannot tell you who approved a change order or submitted a pay app.
- Nobody changes the password. Changing it means telling everyone, so it never happens, even after people leave.
- MFA gets routed around. To keep a shared account working, codes end up forwarded from one person’s phone to the group, which defeats the purpose.
- Credentials spread. Passwords in spreadsheets, texts, and sticky notes are passwords an attacker can find.
The last point matters more than it seems. Payment fraud in construction often starts with one stolen login, which an attacker uses to watch real payment conversations and then send a convincing change-of-bank-account request. Our article on how payment fraud starts with one stolen login walks through how that plays out on draws and retainage.
What does a well-run portal setup look like?
| Situation | Common setup | Better setup |
|---|---|---|
| Several people need the same portal | One shared login for the office | A named account for each person, with roles set by the GC or the portal admin |
| Storing passwords | Spreadsheet, texts, or memory | A company password manager with folders by role, such as AP, estimating, and project management |
| MFA codes | Texted to whoever set up the account | An authenticator app on a company-managed phone, or stored in the password manager, so the code follows the role |
| Portal admins | One person, often whoever signed up first | At least two people at your company who can add and remove users |
| Someone leaves | Hope someone remembers which portals they used | Every portal on a written list, with access removed the same hour |
Most construction platforms let a company add multiple named users, so ask the GC or the platform to set up an account for each person who needs one. For the rare portal that allows only one login per company, keep that login in the password manager so you control who can use it and can change the password in one place.
Where a platform supports single sign-on through your Microsoft 365 account (Microsoft Entra ID), use it. Procore, for example, supports signing in through a company identity provider, in which case your Microsoft account and its MFA control access. As long as the portal is set to require single sign-on, turning off that one account closes every connected portal with it.
How should MFA work when people change phones and roles?
Multi-factor authentication is no longer optional on many of these platforms. Procore requires it for Procore Pay users and is rolling it out to more accounts, according to Procore’s own MFA guidance. The question is not whether to use it but how to keep it from locking you out.
- Use an authenticator app instead of text messages where the portal allows it. CISA’s guidance on implementing phishing-resistant MFA ranks text message codes among the weakest options. Text codes are better than nothing, but they are easy to intercept and they tie the account to one phone number.
- Enroll on company devices. If the authenticator lives on a foreman’s personal phone, the company loses access when the foreman leaves. A managed company phone or tablet stays with the company.
- Store recovery codes. Most portals issue backup codes when MFA is set up. Keep them in the password manager, not in an email.
- Have a second admin. If the only person who can reset MFA is the one who is locked out, you are calling the GC’s support line on deadline day.
This is also one of the first things a GC asks about. If you have ever filled out a vendor questionnaire, you have seen the MFA questions on a GC’s vendor security review. A clean portal setup makes those answers easy.
What should happen the day someone leaves?
Offboarding is where most portal problems start, because nobody has a complete list of what the person could reach. Write the process down once and follow it every time:
- Disable the person’s Microsoft 365 account. Any portal that requires single sign-on closes with it.
- Remove them from the user list in every GC portal on your list, or ask the GC’s admin to do it.
- Change any shared password they could see in the password manager.
- Reassign their portal roles, such as submitting pay apps or reviewing submittals, to someone else so nothing stalls.
- Collect company phones and tablets, and wipe any company data from a personal phone that had email or portal access.
The list in step 2 is the part most companies are missing. If you only build one thing after reading this, build that list. For crews and subcontractors on your own systems, our guide to role-based access for crews and subs covers the internal side.
How do you get started this week?
You do not need new software to make progress. Start here:
- Ask AP, estimating, and each PM to list every portal they log in to. Combine the lists.
- For each portal, note who the admin is and add a second admin.
- Mark every login that more than one person uses, and ask the GC or platform to create named accounts.
- Move every credential into a company password manager and delete the spreadsheet.
- Switch MFA from personal phones to company devices or the password manager, and save the recovery codes.
- Write the five offboarding steps above into your HR checklist.
How does Rudick handle portal access for contractors?
We set it up the way this article describes and keep it that way. Every person gets a named account, credentials go into a company password manager, and MFA follows the person rather than the phone. When someone leaves, one call to us locks every account the same hour, and we reconcile licenses so you stop paying for people who are gone.
We also document every system and login your company uses, and that documentation belongs to you. Our security operations team watches Microsoft 365 around the clock for signs of account takeover, such as sign-ins from unusual locations and hidden mail forwarding rules, which is how stolen portal logins are often discovered. It is part of the managed IT that handles onboarding and offboarding for our construction clients.
Rudick works only with architecture, engineering, and construction firms, so we already know what Textura, GCPay, and Procore look like from the subcontractor’s side.
Get control of your portal logins
Book an Appointment for a login and access review. We will list every portal your team uses, who has access, where the MFA codes go, and what to fix first, so the next pay app goes out on time no matter who is out of the office.
Frequently asked questions
Is it okay to share one Procore or Textura login across the office?
It is better to give each person a named account. Shared logins hide who did what, rarely get their passwords changed, and break when MFA is turned on. Most platforms allow multiple users per company.
Should MFA codes go to text messages?
Text codes are better than no MFA, but an authenticator app is stronger and is not tied to one person’s phone number. Use an authenticator on a company-managed device wherever the portal supports it.
What if a GC portal only allows one login for our company?
Keep that login in a company password manager, put the MFA on a company device, and limit who can open it. Change the password whenever someone with access leaves.
Who should be the admin on our GC portals?
At least two people at your company, usually someone in the office and a senior PM or controller. One admin means one person can lock everyone out by being unavailable.



