Skip to content

Document the Daytona access review connector - #153

Merged
aureliensibiril merged 1 commit into
v2from
aureliensibiril/daytona-docs
Oct 30, 2026
Merged

aureliensibiril merged 1 commit into
v2from
aureliensibiril/daytona-docs

Conversation

@aureliensibiril

@aureliensibiril aureliensibiril commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Why

getprobo/probo#2185 adds the Daytona connector, and its DocumentationURL points to /docs/product/access-review/daytona. This page has to ship with it, or the console's Documentation link 404s.

What

  • New page access-review/daytona.mdx (API key), with a cropped screenshot of Daytona's Create API Key dialog (Restricted selected, no account data).
  • Directory card and sidebar entry.

The caution leads with what a customer must know before handing the key over: it reviews the organization it was created in, and every Daytona key, even one with no permissions, can run processes and read and write files in that organization's running sandboxes. Daytona's own API keys page says the same.

Facts were checked against Daytona v0.226.1 with real keys in a test organization: a Restricted key with no permissions lists members, keys get 401 on invitations, and pending invitations are not listed. The connect steps follow the current console labels. npm run build passes.

Daytona connects with an API key created in the organization to
review. A Restricted key with no permissions selected can list the
members, but every Daytona key can still run processes and read and
write files in the organization's running sandboxes, so the page
leads with that and with picking the right organization before
creating the key.

The collected fields follow the driver: role plus assignments, owners
flagged as admins, and no status, MFA or last login. Pending
invitations are not listed.

The connect steps follow the current console: Settings > Connectors >
Marketplace, then Access Review > Sources > Add sources.

Signed-off-by: Aurélien Sibiril <81782+aureliensibiril@users.noreply.github.com>
@aureliensibiril
aureliensibiril force-pushed the aureliensibiril/daytona-docs branch from fab6c4b to 80af8bf Compare October 30, 2026 16:28
@aureliensibiril
aureliensibiril merged commit 80af8bf into v2 Oct 30, 2026
2 checks passed
@aureliensibiril
aureliensibiril deleted the aureliensibiril/daytona-docs branch October 30, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant