Skip to content
brazosd
Console
User guideTHE FIELD GUIDE

Start with a question

Start hereMeet brazosdDescribe what you want to achieve, bring your materials, and work with an AI assistant toward a result you can actually use. This guide starts from zero, with no programming knowledge required.Start hereComplete your first taskTurn a set of meeting notes into a useful summary. If you have no file ready, paste a short piece of text instead.Everyday workSessions and tasksTreat a session as a workbench for one job: your request, supporting materials, progress, and results stay together.Everyday workFiles and cloud driveKeep input materials and finished work in cloud drive. Choose a location based on who needs access and how the files will be used.Everyday workPractical task examplesCopy these requests and adapt the materials, scope, and output format to your own work. Each example includes something concrete to check.
Search every guideEsc
Browse guides
User guideGo further2 min read

Credentials and authorization

Understand which materials, accounts, and tools the assistant uses, and provide sensitive information through the intended controls.

On this page

Keep secrets out of chat

Use credential management or a dedicated authorization form for passwords, keys, and verification codes. Chat messages, skill instructions, file names, and public descriptions are unsuitable secret stores.

Manage organization service keys in Keys. Give each a useful description and let the assistant use its reference instead of sending the value again.

Secure variables

Think of a secure variable as a named, sealed envelope. The assistant refers to its name, and the execution system substitutes the real value where appropriate. This reduces exposure in model context.

It does not guarantee that an external service, program, or its output can never reveal a secret. Do not ask the assistant to print environment variables or full authenticated requests as a connection test.

Respond to authorization requests

Review the purpose, target, fields, and consequences before completing a form. If a request does not match your task, clarify it before proceeding.

A conversational request for confirmation and a system authorization form are different things. Explicitly ask to review proposed messages, deletions, or purchases before execution.

Payments

Review product, quantity, total amount, commission, and source before approving an order. Cancelling payment and stopping other task activity are separate actions.

Options such as skipping future questions for a product category affect later behavior. Ordinary model and resource usage may accrue without a separate order-payment dialog for every step.

Access boundaries

Access depends on the task's identity, organization, groups, device scope, model settings, tools, and external service rules. Rephrasing a request does not grant extra permissions.

Check the current organization and resource ownership, then ask an authorized administrator for the necessary change.

Public sharing

Review audiences before publishing a skill, creating a share link, or placing files in public storage. Internal availability is not a reason to make content public.

To stop public access, revoke the actual share or remove the public resource, then verify its state. Saying “stop sharing” in conversation does not by itself invalidate a link.