Intermediate Admin access level that allows additional invites within that company.

[kmulase]

We want to see an intermediate access level between "Admin" and "Member."

This access level would allow that user to invite additional users from their organization only to the project. 

As consultants, we want the ability to staff up a client's project when required, especially for deadlines. Currently, we need to wait on the client admin to add users, which can sometimes take a while and is therefore not ideal for deadlines or when our users are out of the office. If we need another engineer or BIM specialist, it's entirely out of our hands, and hampers our ability to serve our clients.

[Chad-Smith]

And as someone on the other end who administers projects and adds users, I would love to allow Companies to add additional members from their same company. Using the member's email domain might be a good way to allow this.

I think the hard part would be deciding which ACC modules the added user should have access to? Maybe the same module/s as the user who is performing the adding? Which could then lead onto consuming project host licenses without host approval?

I think the safest way to implement this feature, at least to begin with, is for users who need to bring their own license, such as BIM Collaborate Pro.

[timothy_stark]

I agree with Chad Smith, I should be able to add a "company Admin" person and let that person add their team members as they see fit.  I.E. - I add an A/E firms Project Manager, and that project manager can add the Electrical engineer, the mechanical engineer, drafter, etc. Privileges would be limited to a subset of the "company admins" privileges.  In it's current fashion, it is placing too much burden on the project owner/admin to add all these people and ensure their access levels are correct etc.

[walter_hoffman3]

I concur

[timothy_stark]

To add to this, it would further help if that "company admin" role could designate a sub contractor to be a "company Admin" for their company as well.  I.e. - A/E has a subcontractor that is the commissioning agent, that person could then add people in their company as well.  I realize this is adding a whole lot of complexity but I do beleive products like Procore and Submittal Exchange allow you to do this. 

[adbryson]

We need this sooo badly!  It is very frustrating to live in a world where we need to get into a model to make changes, but that person available to help has not yet been invited to the project by an external company/admin, and the project goes out in less than a day.  Then the access request never gets attention for hours, or worse, not until the following day.

[Chad-Smith]

In the Jan 2026 release there is now the ability in the Account Admin to assign certain roles with Member Management permissions.

This is a great first step, but it stops short of enabling the request/s in this Idea thread.

I've mentioned it before, but allowing us to record an email domain with a Company will go a long way.

• First and foremost, it would provide the first line of permissions to allow that Company to invite their own Members.
• When adding a Member, their email domain provides a 'lookup' value to automatically find and assign the correct Company to the Member.
• The Company record would need the ability for the Account Admin to record default Roles. e.g. An Architecture Company would be assigned Architect. This would provide a restrictive measure so that a Company can't assign themselves non-default Roles. This would be a security measure to stop the Company from accessing other role's information, but it could be overridden by a Project Admin on a per project basis.
• Email domains that are linked to a Company could be used as a real-time auditing measure to check if a Member is incorrectly assigned to a Company. i.e. A Project Admin is adding a Member and the incorrect Company is selected. A warning prompt could be displayed. It wouldn't stop them from doing this in case it is deliberate, but it should at least make them question their Company selection.
• Lastly, I think there would need to be a Project level toggle to disable this, for the more secure projects where each Member may need to be vetted and authorised before adding.

In my previous reply, I commented on which modules they could assign and access. But on reflection, the Account Admin Role definitions should already be managing this.

In summary:

• Company records need attributes for Email Domain and Default Role/s.
• Projects need an override toggle to disable it.

[kmulase]

Agree with @Chad-Smith thanks for bringing further clarity to this.