Understand access and permissions.

Your project and its services

Your connected GitHub repository holds the project source and its version history. A project preview is a separate environment for running and reviewing that code; it is not the same thing as publishing your application.

• Project access distinguishes owners, editors and viewers. An invitation gives the role assigned to that collaborator, rather than ownership of your connected accounts.
• Database access and public hosting are separate connections. MaShop has a native Netlify integration, but the project conversation can address another provider and the connection it requires.
• Review the code, configuration and service permissions before using a generated application with private records or real transactions.

Information used by the AI

Answering a request can involve your prompt, relevant conversation context, project files and results returned by an authorized tool. That information may be included in a model request. MaShop’s current inference client uses Fireworks.

An action on a connected service also sends the arguments needed for that action to the service. A web search sends its search terms outside the workspace. Include only the information the task needs, and keep passwords, recovery codes and private API keys out of ordinary messages and searches.

Agents and tools have distinct permissions

Connecting an account makes its supported tools available. It does not authorize every action. Tool permissions and the agent’s autonomy setting determine whether an action can proceed, needs approval or is blocked. Code uses the same tool approval path when calling connected MCP tools.

• Read the proposed action, target and arguments before approving it. Payment actions require the corresponding payment approval permission.
• Review the execution result after signing. An approved request is not proof that the external service completed it.
• A collaborator’s project role also limits what they can change, run, sign or revoke. The connected provider may impose further restrictions.

Connection credentials

New native OAuth tokens and MCP OAuth credentials are encrypted by MaShop’s server before storage in production, using AES-256-GCM. The connection flows require encryption to be configured before writing these credentials.

MaShop needs server access to the credentials required for an authorized operation. Encryption does not remove that access, and a connected provider still processes the operations sent to it. Use the connection flow or designated credential field rather than pasting a secret into chat.

Protect sign-in and recovery

Two-factor authentication is available in account security settings. An authenticator setup becomes active after its verification succeeds. MaShop limits repeated setup and recovery requests.

• Recovery codes are single-use; the stored records contain their hashes. Save the codes privately when they are shown.
• Generating a new recovery set replaces unused previous codes. Keep your current set separate from your sign-in device.
• Never share an authenticator QR code, secret or recovery code with an assistant or support. Two-factor authentication protects sign-in; it does not replace careful tool permissions.

Review connected access

Native project integrations and MCP servers are different connection paths. A server’s actual tool catalog and the account you authorize determine what it can do. A cloud service connection does not, by itself, give an agent control of your computer.

• Check the connected account, available tools and permitted actions before starting a task.
• When an authorization is no longer needed, disconnect it in MaShop and review the authorization at the provider as well.
• Removing access does not undo earlier actions or retrieve data already sent to a service. Consult the privacy policy for the current information about processing and your requests.