Answer: The security notes state that the token never touches the browser, PKCE binds the code to the backend's code_verifier, codes are single-use and expire after 10 minutes, callback URLs are allowlisted, you should verify the code is for the requesting user, and outpost_name is only a suggestion since the admin may override it. Status: Confirmed Entry: tool/devin/permissions-and-security/outposts-partner-security-notes Revision: 1 Digest: sha256:a6fddeaa5b7c1ca7 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:12:32Z Last changed: 2026-11-13T03:12:32Z Last verified: 2026-11-20T12:41:34Z Next check: 2026-11-21T12:41:34Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Token handling | The token never touches the browser. | | [1] | 2026-11-20 PKCE binding | PKCE binds the code to you. | | [1] | 2026-11-20 Code expiry | 10 minutes | minutes | [1] | 2026-11-20 Code single-use | Codes are single-use and short-lived. | | [1] | 2026-11-20 Callback allowlisting | Callback URLs are allowlisted. | | [1] | 2026-11-20 User verification | Verify the code is for the requesting user. | | [1] | 2026-11-20 outpost_name | Keep `outpost_name` sensible. | | [1] | 2026-11-20 Sources: [1] Cognition. "Devin Outposts partner integrations". https://docs.devin.ai/cloud/outposts/partners.md Role: primary. Accessed: 2026-11-20T12:41:34Z Quote: "**The token never touches the browser.**" (Supports: Token handling) Quote: "**PKCE binds the code to you.**" (Supports: PKCE binding) Quote: "it also expires after 10 minutes." (Supports: Code expiry) Quote: "**Codes are single-use and short-lived.**" (Supports: Code single-use) Quote: "**Callback URLs are allowlisted.**" (Supports: Callback allowlisting) Quote: "**Verify the code is for the requesting user.**" (Supports: User verification) Quote: "**Keep `outpost_name` sensible.**" (Supports: outpost_name) Published: 2026-11-20T12:41:32Z Snapshot SHA-256: 8c89d2bfe4cbbb8d71c92043b5071f4653eeec19c4474760e984546ab2690267 (captured 2026-11-13T03:12:31Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:12:32Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:41:34Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:41:34Z Last attempt: 2026-11-20T12:41:34Z Notes and limitations: Extracted automatically from a single official source (section "Security notes"). Related: https://latestn.com/tool/devin/permissions-and-security/outposts-token-scopes What API token scopes does Devin Outposts require for reading and writing? https://latestn.com/tool/devin/permissions-and-security/preview-access Who can open a Devin browser preview link? https://latestn.com/tool/devin/permissions-and-security/profile-restrictions-overview What can I restrict in a Devin security profile, such as network, MCP, git, and GitHub CLI access? https://latestn.com/tool/devin/permissions-and-security/oidc-security-properties What security properties does Devin's OIDC token provide, such as expiration and revocation? https://latestn.com/tool/devin/permissions-and-security/oidc-token-claims What token claims does Devin include in its OIDC identity tokens? https://latestn.com/tool/devin/permissions-and-security/outposts-api-token-scopes Which API token scopes does Devin Outposts require? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:12:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/permissions-and-security/outposts-partner-security-notes/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/permissions-and-security/outposts-partner-security-notes POST: https://latestn.com/dispute/tool/devin/permissions-and-security/outposts-partner-security-notes with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/permissions-and-security/outposts-partner-security-notes?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What security considerations apply to Devin Outposts partner integrations? Revision 1, last verified 2026-11-20T12:41:34Z. https://latestn.com/tool/devin/permissions-and-security/outposts-partner-security-notes (accessed 2026-11-21T09:56:56Z). @misc{LatestN_tool_devin_permissions_and_security_outposts_partner_security_notes_r1, title = {What security considerations apply to Devin Outposts partner integrations?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/permissions-and-security/outposts-partner-security-notes}}, note = {Revision 1; digest sha256:a6fddeaa5b7c1ca7; last verified 2026-11-20T12:41:34Z; accessed 2026-11-21T09:56:56Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/permissions-and-security/outposts-partner-security-notes