plugin.space / Flows

Flows by plugin.space

Access information

Understand which features are available to your account and how your flows are stored.

On your computer

Create, edit, capture and present up to 3 active local flows without an account. This limit covers the local library on this computer across projects. Archive a flow to free a slot; local files are preserved, and archived flows must be restored when a slot is available before opening or exporting them in Flows. Your local documents and screenshots remain on your device; connecting an account also enables private Cloud saving by default.

Account storage

Cloud storage is optional. Sign in on the account website to connect an existing account. Signing in does not start a purchase. Connecting the local plugin enables private Cloud saving for opened and new flows, with limits and features according to the account plan. Explicit per-flow opt-outs are preserved. Local and cloud slots are counted separately.

Saving depends on the storage permissions already available to your account. If saving is unavailable, Flows explains that restriction and keeps your local work available. An existing account may also provide access to a larger local library. The viewer shows your current allowance. Confirmed local access can remain available offline for up to 7 days, never beyond its validity period. After it expires, up to 3 local flows stay active; the remaining local files are preserved, but their flows must be restored to an active slot before opening or exporting them in Flows. Disconnecting the local account clears its cached access. Cloud writes and invitations are also subject to fair use safeguards against bursts or unusually large automated libraries. If an operation is paused, the service explains the restriction and reading/export remain available. Contact support if ordinary use is affected. This page does not change your permissions.

Viewing and sharing

You can view saved flows that you own or that another person has shared with your verified email. There is no limit on invited viewers. All invited viewers can comment on active cloud flows, within storage and discussion limits. Only the owner can grant or revoke access. In Share this project, select the saved flows to include. Invited people must sign in with the invited email; Anyone with a link allows anyone holding the URL to view the selected current flows and captures without signing in. Public links exclude comments and retained history. New project flows are not automatically added. Owners can change the selection or disable public access; copies already obtained cannot be recalled.

User types, test scenarios and quality review

The workspace can group flows by the user types recorded in their role audits. Open a role to inspect its source evidence, permission conditions and unresolved questions. These roles describe the mapped application and do not control access to your Flows account or shared documents. Older flows stay unclassified until their roles are assigned.

The Test scenarios panel includes functional test drafts, use cases and quality-evaluation suggestions derived from a flow. You can filter them by role and export the selection as functional JSON or Midscene Test YAML, or as quality JSON or Markdown. All remain drafts for review; generating them does not execute tests or research. Cloud viewers rebuild these materials from the saved source graph and hints. Creating or changing the source map requires the desktop workflow with local execution.

Connection and sign-in

Enter sign-in details only on the account website. The local viewer receives a separate connection that expires within 24 hours. You can disconnect it from Flows or review and revoke individual or all plugin connections in your account settings.

Assistant panel

The MCP connection opens saved and shared account flows beside your conversation. The hosted MCP connection reads permitted diagrams, captures and discussions. Owners can separately authorise sharing access to manage the selected flows, invite or remove people, and enable or disable public link access in the panel; including retained history requires an additional choice. Version comparisons require the owner’s active Pro access and, for a teammate, a separate history grant. The hosted connection cannot upload local files, edit saved flow content, comment or delete flows. Manage those changes on the account website or in the trusted local plugin. An older write permission does not grant sharing access. Your selected AI host can receive flow contents, screenshots and source references, plus the account identity used for the connection. The desktop local MCP variant opens unsaved project flows in the same panel. Connecting a local account enables private Cloud saving for opened and new flows, including captures, while its viewer or panel is active. Automatic updates are bound to that account; explicit opt-outs and preferences for another account are preserved. Pro records previous versions on changed saves. Sharing and sharing retained history remain separate choices. Panel-only labels rely on the host enforcing them and are not independent proof of a human click. The hosted service checks the granted sharing permission, connected account and flow ownership before changing access.

Connect through your assistant and confirm access on this website. Assistant connections last up to 30 days, with short-lived access tokens. Disconnect the current connection from the panel or through the host’s connection settings. Your account settings list local and assistant connections and let you revoke one or all of them; the consent page also lets you revoke all assistant connections.

Need help?

If access does not match what you expect, contact support. Include your account email and the message you see, without passwords or sign-in codes.