integrations

Your team can now use Google Workspace or Okta alongside Microsoft Entra ID to sign in to Specset. Google Workspace setup is coordinated with Specset support. If you already have an account, the Google connection flow verifies your existing sign-in and asks you to confirm the link, keeping your projects and memberships together.

Passkeys let you sign in with your fingerprint, face, or device PIN when your organization allows them. Account Settings now separates Profile from Sign-in & security, where you can manage passkeys, your password, email verification, and recovery options. New password checks reject common or easily guessed choices, and sensitive changes ask you to verify your identity when needed.

In Org Settings → Security & SSO, administrators can make SSO optional or required, choose allowed sign-in methods, and require MFA or phishing-resistant MFA. Authentication, onboarding, and session-duration changes stay in a draft until you click Save. Specset checks that you can meet the proposed policy before applying it. Each organization's sign-in requirements still apply when you switch between teams.

See Single sign-on, Account security, and Organization security for setup and recovery instructions. Authenticator-app setup is not yet available; passkeys and qualifying SSO are the available routes for stronger authentication.

Specset is now available as a native plugin for both Claude and Codex. Install one bundle to give either agent the project context and construction workflows it needs.

• Nine shared skills. Search specs and drawings, set up projects, manage submittals and RFIs, work with closeout records, ask project agents, and administer your organization.
• Native MCP tools. Search and read structured Specset content directly, with the same tool registry on both agents.
• Secure sign-in. Local plugins use browser or device authorization through the Specset CLI. Hosted ChatGPT connections use organization-scoped OAuth.
• File transfers. Claude and Codex can stream local uploads and downloads through the CLI. Hosted clients can pass attachments and receive short-lived download links through MCP.

The plugin defaults to read-only work and asks before changing project data. Credentials stay in the local CLI or the hosted OAuth connection rather than in the conversation.

Follow the setup guides for Claude and Codex.