Subject: Altium 365 Collaboration Workflow (Internal A365 Team Memo)
To ensure our design process remains agile while maintaining strict control over our production libraries, we are adopting a "Guest Editor" model for our Develop tier collaborators and external partners.
Why we are using Guest Access:
Security & Focused Access: Guest seats allow us to grant access to specific projects only. This ensures that collaborators see only the data relevant to their current task, keeping our broader workspace secure.
Library Integrity: To maintain our ISO/Internal Quality Standards, only core team members (Agile/Pro) can modify "Released" footprints and symbols. Develop users acting as Guests can use our verified components but cannot accidentally alter them.
Cost & Resource Efficiency: By using Guest invites, we avoid consuming permanent workspace seats for short-term or specialized contributors, allowing us to scale our team size dynamically.
Project Leads: When inviting a Develop user, please use the "Can Edit" permission level but do not add them as a "Workspace Member." This keeps the project history clean and the permissions compartmentalized.
What this means for the Altium Develop User (Guest Editor):
They will receive a project-specific invite, which they can edit and save to the A365 Server.
