We’re encountering a workflow limitation in BuildingConnected where users are restricted to accessing only one company per email account. This constraint is especially challenging in environments where employees need to interact with multiple BuildingConnected spaces for proposal uploads and project collaboration.
Because BuildingConnected is tied to Autodesk SSO, we’ve had to implement workarounds that introduce operational inefficiencies and potential security concerns. These include:
- Creating separate user accounts with unique emails, requiring private browser sessions to avoid credential conflicts.
- Using shared accounts with complex passwords and device-specific passkeys, which adds friction and increases administrative overhead.
- Assigning departmental champions to manage uploads, which centralizes responsibility but reduces agility and scalability.
We’re currently using the shared account workaround, but it’s not ideal long-term. A native solution that allows a single user to securely access multiple BuildingConnected companies would significantly improve usability, reduce risk, and align better with enterprise identity management practices.
