Skip to main content


Today, we’re excited to announce new Team API endpoints - designed to give you programmatic control over how your teams are created, maintained, and managed in Lucid.

You can now:

  •  Create, archive, or restore a team
  •  Add or remove users from a team
  •  List users or teams to audit org structure

🔗 Explore the API docs →

Why it matters:

In many organizations, content ownership is still too tightly tied to individuals. This way of working leads to lost knowledge during role changes and offboarding.

With Lucid’s Team Hub experience and this new API layer, we’re helping teams:

  • Encourage collective ownership and automate context when roles shift
  • Systematize org-wide collaboration and document retention
  • Organize Projects with intentional space and team ownership
  • Deploy and manage teams at scale - backed by your internal identity sources (AD, Okta, CSV, etc.)
     

If you’re thinking about how to scale collaboration or reduce doc sprawl in the next year, we’d love to hear from you.
 

📩 Reach out with questions, ideas, or your own use cases.

When teams are aligned, innovation accelerates.

— The Lucid Developer Platform Team

 

Thank you for the update ​@Jaxson Perry . This is exciting news!


Is there any way to generate an api key which has only access to a specific team and not the complete account ? 


Hey ​@janpi , thanks for the question. I’m not completely sure I understand your question, but let me answer it the best that I can.

 API Keys are owned by the user who created them, not the account, and can only have access to the same teams the user already has in Lucid. All users can see all open and closed teams on their account, as well as the hidden teams they are a member of. However, they can only edit teams they are members of. Admins can sometimes have additional visibility and edit access if permitted by your account owner.


When you create an API key, you can choose to give it Edit access to teams or Readonly access to teams, or to not give it access to teams. Permissions for teams are only limited this way, and can’t be limited on a team by team basis.

Hopefully this answers your question! If not, please clarify with another question.


Reply