Last updated: 2026-10-25

Glance Docs

Use these guides to sign in, connect Claude, request work from agents, review website changes, and understand what a campaign task has produced. Features depend on the tools enabled for your workspace; check the actual task, asset, preview, or live page before treating work as finished.

Who This Is For

• People setting up a Glance workspace and the Claude connector
• Teams running an interview or reviewing its outputs
• People requesting and approving website or campaign work

Where To Read This Guide

Read these pages at docs.getglance.com. The repository source is docs/user-guide/; published pages update when the Glance web app is deployed.

Start Here

1. Start Here — sign in and connect Claude.
2. Onboarding — prepare, save, and transfer interview inputs before requesting work.
3. Which Channel Do I Use? — choose a supported request channel.
4. Request Changes On Your Website — request and review website changes.
5. Work With Your Glance Agents — create, assign, and review tasks.
6. Marketing — distinguish task drafts, saved assets, and sends.
7. Troubleshooting — resolve common blockers.

The Brand Interview, Connect Claude, and Migrating from ChatGPT guides provide more detail.

What To Expect

An interview is a conversation. Ask for one question at a time, share concrete examples, and review the output your workspace actually saves. A requested output is not proof it was saved or published: open the result and ask your operator if it is missing.

Last updated: 2026-10-25

Start Here

This is the fastest path to using Glance with Claude.

1. Sign in with your magic email link.
2. Add the Glance connector to Claude.
3. Authenticate the connector.
4. Prepare a brief for the deliverable you want, then run only the interviews that supply its inputs.
5. Ask for a change: see Which Channel Do I Use?.

Want the full path from interviews to a work request? Read Onboarding: From First Interview To A Work Request.

If you are new to Claude, read this page first. If you are moving from ChatGPT, the next section explains the differences that matter most.

The Claude settings labels can change; use the current Connectors screen.

1. Sign in. Start by opening your Glance workspace and signing in with the account your team invited.
2. Find the workspace. Check the company and workspace shown in the app before you create anything, especially if you belong to more than one team.
3. Choose a path. For work that needs an owner and a review trail, use the task board. For conversation, use a channel your team has already linked.
4. Check the result. Write the outcome you want, add any useful links, then check that your request appears on the board. That confirms it was received; a later status and review confirm the work.

What You Need

• Your tenant login email
• Claude desktop or Claude web
• The Glance connector URL for your tenant

Magic Email Login

1. Go to app.getglance.com.
2. Enter the same email address your team gave you.
3. Open the magic link from your inbox.
4. You're returned to the tenant workspace, signed in.

If the link expires, request a new one. Do not keep trying an old link.

Add The Connector

In Claude, open Settings, then Connectors, then Add custom connector.

• Name: Glance
• Remote MCP server URL: https://connector.getglance.com/mcp

Click Add, then click Connect. A browser tab opens for authorization. If your sign-in has expired, use the same invited account to sign in again. Check the workspace shown, approve the authorization screen, and return to Claude.

Claude Desktop: first check whether the connector appears in a new chat. If it does not, refresh connector settings or restart the app, then check again.

Confirm It Worked

You should see the connector as connected before starting the interview. If the wrong tenant appears, stop and reconnect before proceeding.

Last updated: 2026-10-25

Onboarding: From First Interview To A Work Request

This guide helps you gather useful source material, save and retrieve each interview result, then request one concrete deliverable. An interview organizes information; it does not automatically build a site, webinar, campaign, or design system. The available tools and saved outputs vary by workspace. If an output cannot be opened by you or transferred to the assigned work, ask the Glance team for an accessible copy before relying on it.

Start here

1. Sign in and connect Claude using Start Here.
2. Describe the deliverable you want. Ask Claude to prepare a plan and ask clarifying questions one at a time.
3. Complete only the interviews that supply inputs for that deliverable.
4. Review and save each interview output. When the needed inputs are ready, create or update one project task and attach the approved, accessible inputs.
5. Review the task and its output. Use Marketing for the difference between a task draft and a saved campaign asset.

Do not ask for a build until the required source material is ready. If a similar task already exists, update it instead of creating a duplicate.

Planning before a request

Prepare the request in Claude or your tenant's assistant before submitting it to an assigned task channel. If New Task shows Auto mode, open its menu, choose Plan mode, and check that the closed button now reads Plan mode before selecting Create Task when you want a proposal first. If the picker is absent, review and approve the brief in Claude or your tenant assistant before submitting an assigned request. The exact approval control and action that starts implementation still need verification in your workspace. Do not rely on a sentence such as “plan only” to prevent an assigned task from starting.

Copy and adapt:

I want to [deliverable and intended outcome] for [audience]. First help me prepare a plan: ask one clarifying question at a time, identify required source material and missing facts, then show the proposed scope, deliverables, assumptions, and success checks. Do not create or assign a task until I approve this brief.

Review the plan, correct assumptions, and approve the brief yourself. Then submit it as a task request with the exact deliverable and review boundary. If Glance Agents shows question or plan-review cards, follow Questions and plan reviews to keep answers and decisions attached to the right request.

Which decision am I making?

1. Approve the source brief. Read and correct the facts in Claude or your tenant assistant. This prepares the input; it does not create a task or accept a saved Glance Agents plan.
2. Choose Plan before creating the task. If New Task offers the mode picker, choose Plan mode and check the closed control before submitting. Opening the menu alone does not select it. If the picker is missing, approve the brief before assigning work; an ordinary assigned task can start work.
3. Review the saved plan. If a Plan tab appears, read its current revision. Answer questions using their own cards. If a plan confirmation appears, check that it concerns the revision you read. Request a revision or accept using that card's controls. Acceptance can start implementation; it does not show that implementation finished.
4. Review the produced result. Open the exact output, request any correction, and reopen the revised version. A promise in a comment does not confirm that the output changed.
5. Check publication separately. Keep any publication restriction explicit. After publication is reported, check the live result. Approving a plan or draft does not establish that the page is live.

The interviews

Interviews are guided conversations. Start by name in Claude, answer with concrete examples and links you are comfortable sharing, and ask for a recap of what was saved. Resume by asking for the saved interview or artifact by name. A filename or server location alone does not prove you can retrieve its contents.

The exact filenames and tools can vary. Ask Claude to show the result, tell you where it is saved, and reopen it. If you cannot read it, contact the Glance team rather than copying a path that only works on a server.

Use the starter requests below in Claude with Glance connected. Replace the bracketed text. If the assistant cannot find the named interview, ask your workspace team to check the connection before continuing.

Brand interview

Start the Glance Brand interview for [company]. Ask one question at a time. Use [current site and approved examples] as source material. Tell me if this connection cannot start the interview.

Review the positioning, audience, and differentiators. See the detailed Brand Interview guide.

Voice interview

Start the Glance Voice interview for [company]. Ask one question at a time. Use [approved writing examples] and ask what I like or dislike about them. Tell me if the interview is unavailable.

Review the guidance against real writing you would send. Correct examples that sound unlike your business. Use the approved guidance in copy and email requests.

Offers interview

Start the Glance Offers interview for [company]. Ask one question at a time. Use [product pages and confirmed pricing source]. Ask me about missing facts instead of inventing them. Tell me if the interview is unavailable.

Check the audience, products, prices, terms, proof, and links. Keep unconfirmed claims and missing dates visible as open questions. Use this output for website, webinar, or campaign planning.

Site Architecture interview

Start the Glance Site Architecture interview for [company] and [website outcome]. Use [current URL and approved offer]. Ask one question at a time. Tell me if the interview is unavailable. I am requesting a page and navigation plan, with no build or publication yet.

Check that the proposed pages and navigation support the action you want visitors to take. Give the approved page list to a separate website task.

Webinar interview

Start the Glance Webinar interview for [event and audience]. Ask one question at a time. Use [approved offer and source material], and flag missing dates, registration links, or claims. Tell me if the interview is unavailable.

Review the event purpose, audience, presentation outline, offer, and missing facts. A saved brief is an input to a presentation or event request; check separately whether that asset was created.

Campaign interview

Start the Glance Campaign interview for [campaign outcome and audience]. Ask one question at a time. Use [approved offer and timing], and flag unconfirmed facts. Tell me if the interview is unavailable. Do not schedule, publish, or send anything.

Review the channels, timing, intended result, and open questions. Request the named draft assets separately and check where each is saved.

Resume, review, and retrieve an interview

For each interview above:

1. Answer the questions with your facts and examples. If you return later, use this request:

Resume my [interview name] interview for [company or event]. Show the last completed question and the next question, or tell me if this chat cannot access it.

1. Before using the result, ask for the complete content:

Show the complete [interview name] result you actually saved for [company or event], including unresolved questions. Tell me where I can reopen the same complete content. If nothing was saved or I cannot access it, say so. Please show the full text, not just a filename, server path, or summary.

1. Read it, correct wrong facts, and ask to see the corrected version. Keep a copy you can open. If no accessible result is provided, stop and request an accessible copy from the Glance team before assigning work that depends on it.
2. Reopen the saved result and check that it contains the version you approved. Then follow Request work from interviews below. Finishing the conversation does not automatically create a website, presentation, or campaign.

Request work from interviews

Save each interview's approved output. When the inputs for your chosen deliverable are ready, create or update one task in Glance Agents. Transfer the complete approved output through an attachment or other tenant-accessible content supported by the task. Confirm the uploaded content can be opened after reloading the task. A filename, session name, or server path is not proof of access. Keep manual handoff as the process until an automated transfer has been demonstrated in your workspace.

Check the assigned agent's access too: ask it to identify a detail found only inside the approved content, such as a format or example you did not repeat in the task request. Compare its answer with the source. If it cannot read that detail, stop and request an accessible handoff before relying on its work. This check is separate from confirming that you can open the attachment yourself.

Add the deliverable, intended audience, source links, required output format, open questions, and review boundary. Assign to the owner shown in your workspace. Do not create six tasks just because you completed six interviews.

Website request

Prepare a plan for [website/page deliverable] for [audience]. Use the attached approved Brand, Voice, Offers, and Site Architecture outputs, plus [source links]. Identify missing facts before drafting. Deliver [specific pages/content] as a reviewable draft or preview. Do not publish. Tell me what was saved and where I can open it.

Webinar request

Using the attached approved webinar brief and source material, prepare [presentation/script/event asset]. Confirm [date, duration, audience, registration link] and flag any missing facts. Provide a reviewable draft and tell me where it is saved. Do not publish, schedule, or send invitations.

Campaign request

Using the attached approved campaign brief and source links, propose a campaign plan and list the specific draft assets you can create in this workspace. Draft [asset names] for review only. Identify missing facts and show where each saved asset can be opened. Do not schedule, publish, or send.

Email request

Draft [email purpose] for [audience] using the attached approved Voice and Offers inputs and [source links]. Use placeholders for any unconfirmed date, price, link, or sender. Tell me whether the result is only a task comment or a saved Campaigns asset, and show me the saved version and its Details. Do not schedule or send.

Review and next action

A task comment or completed task may contain a draft without saving it elsewhere. Check the actual asset or preview, correct it on the task, and reload to confirm the revision. Then identify the next separate action: publication, scheduling, or sending. Review and completion do not perform those actions automatically. Verify publication on the live page and verify a send in the sending service.

Getting help

Contact team@mail.getglance.com with the task link, interview name, what you expected, and what you could actually open. Do not include passwords, API keys, or private server paths.

Last updated: 2026-11-02

Which Channel Do I Use?

There are three ways to ask Glance for a change. Pick the one that matches what you want to do.

1. The review widget on your site's review copy

Use this when you want to request a change against an existing page. Available actions depend on the site and workspace.

How: open the review copy using the action available in your workspace and follow the panel. The written guide is in Request Changes On Your Website.

What happens next: review the changed page on the review copy. Keep its URL separate from your live public page. An Accepted request does not confirm that the live page changed. Follow Check the live result after publication is reported.

The review widget may support requests beyond text, depending on the site and workspace. Check the options and response shown in your workspace. If the requested change is declined or the needed action is unavailable, use a New Task or contact the Glance team.

2. A New Task in Glance Agents (preferred for everything else)

Use this when you want a layout or design change, a new page, a campaign, an email, or anything the widget refuses.

How: open Glance Agents, click New Task, describe what you want and assign it to the owner shown in your workspace. Step by step: Work With Your Glance Agents.

What happens next: follow the task and any child task or review card your workspace provides. A review decision or completed task does not itself publish the change. Confirm the separate publication path with your workspace team and open the live page after publication.

3. Telegram /create to @getglance_bot

1. Use the linked chat. Open the Telegram chat your team has already linked to its Glance workspace. Do not connect a different bot or rebind the chat. Prepare your request first: /create can assign work immediately, so say explicitly if you want questions or a plan first.
2. Create a task. Start with /create and a short, complete request. Keep a detailed brief in Glance Agents, where you can inspect its contents and assignment. Do not assume a long Telegram message becomes a full task description.
3. Check the board. Check the response and open the corresponding board task. Confirm the workspace, saved request, and assignee before assuming it landed correctly. If there is no matching task, keep the receipt and contact the Glance team before sending the same request again.
4. Continue in the task. Put follow-up details and feedback in the task thread so the work stays visible. Ordinary chat is not a reliable way to create a tracked task; use slash create and verify the board.

Use this when you are on your phone.

How: open the chat with @getglance_bot. Start your message with /create, then describe the change.

Example short request to send in your linked Telegram chat:

/create Help plan a feedback survey after our workshop. Ask me about the audience, reply collection, and reviewer first. Questions only for now. Do not send, publish, or fetch contacts.

For practice, use a fictional workshop and sample answers. For real work, use your actual audience and approved information. When questions arrive, answer them on the matching task, then check that the answers are saved there. Ask for a survey plan next, review it, and request a draft only when that plan is ready. If no questions arrive, follow the task's status and owner using Work With Your Glance Agents.

"Questions only" is an instruction to the agent. It does not turn on a separate Plan mode or pause the assigned task automatically. Review the task before asking it to continue. For a complete example of questions, saved answers, a plan, and a separate draft request, see Marketing.

What happens next: when the linked command succeeds, it should create a tracked task. Use the bot's receipt and the saved board task to verify the workspace, saved request, and assignee. A bot receipt alone does not confirm that the agent finished the work.

Use /create explicitly. A free text message is not a reliable way to create a board task; check the bot's task confirmation before assuming it was filed.

Watch: Create A Task From Telegram

This recording uses the fictional Practice Studio workshop page. It shows one /create request, the new task on your board and the plan that waits for your decision. Your Telegram account must already be linked to your workspace; that one-time step is not shown.

Staging example: Send one /create request to the Glance bot in Telegram, find the new task in Glance Agents and see its plan waiting for your approval0:00 Why use Telegram0:10 Type the request0:21 The bot replies0:28 Find the task in Glance0:41 The plan waits for you0:59 What you have nowRead transcriptListen to audioApprove and Reject are not clicked, so nothing is built. Your Telegram account must already be linked to your workspace; that one-time step is not shown. The Telegram part is a real capture of the Glance bot chat with earlier messages and account details hidden, and the other tasks in the list are hidden too. Telegram sets no mode, so the task page shows no mode label; here the CEO agent wrote a plan that waited for approval, and other requests may behave differently. The agent can later post a notice that it did not produce a reply; the written steps say what to do.Actual staging recording with narration and captions; the plan waits for approval and nothing is built or published.

1. In the chat with the Glance bot, type /create and then a short, complete request, and send it once. The request becomes the task title. The example was: /create Change the start time on the practice workshop page from 10 am to 10:30 am. Show me a preview. Do not publish.
2. The bot replies with the new task number. In the example it sent two short messages that carry the same number.
3. Open Glance Agents and go to Tasks. Click the search box and type part of the title, such as "start time". Open the task that has the number the bot gave you.
4. Under the title, a note reads Requested via Telegram. In the example the CEO agent wrote a plan within about 40 seconds. A card asks Do you accept this plan? with Reject and Approve. The recording clicks neither.
5. Reload the page. The plan and both buttons are still there.

Telegram only creates the task; you still decide on the board. A comment is never approval, and nothing is built until you choose Approve, and approving a plan does not publish anything. Telegram sets no mode, so the task page shows no mode label, and a different request may start differently, so open the task and read what it says. If a notice later says the agent did not produce a reply, wait a moment; if nothing new appears, send the word continue in the task.

Which one is better?

Both channels are intended for tracked task requests; verify the saved task after submitting. Use New Task when you need to inspect the assignment or include a detailed brief before submitting. Use /create for a short request whose next action is clear, including a request to ask questions first.

An email request filed through either channel is a task on the board. A CEO or CMO may return a brief or draft there when available. A draft in its comments is not yet a saved campaign email or permission to send. See Marketing for the email's own revision, review, and sending steps.

Stuck?

Email team@mail.getglance.com.

Last updated: 2026-10-25

Brand Interview in Claude

This guide shows tenants how to use the Brand Interview connector inside Claude. The interview helps collect brand context in a conversation. Review and save the result that your workspace actually provides; a transcript, brand document, design system, or preview is not guaranteed.

Back to main guide

What You Need First

• Access to your tenant workspace
• A verified email address for magic email sign-in
• Claude desktop or Claude web access
• The Brand Interview connector URL for your tenant

If your team gave you a connector URL, use that exact URL. In most cases it will be https://connector.getglance.com/mcp.

1. Sign In With Magic Email

1. Open your tenant login page.
2. Choose email sign-in.
3. Enter the email address your team has on file.
4. Check your inbox for the magic link.
5. Open the link to finish signing in.
6. Return to the workspace after the browser confirms you are logged in.

Tips:

• Use the same email address you will use to connect Claude.
• If the link expires, request a fresh one rather than reusing an old email.
• If you manage more than one tenant, be careful to sign into the right one before continuing.

2. Add The Connector To Claude

1. Open Claude.
2. Go to Settings, then Connectors or Integrations.
3. Choose Add custom connector.
4. Paste the connector URL your team provided.
5. Save or continue.
6. Wait for Claude to open the authorization flow.

If Claude asks for an account, use the same email address you used for tenant sign-in.

Using Claude Desktop instead of claude.ai? Check for the connector in a new chat first. If it does not appear, refresh connector settings or restart the app, then check again.

3. Authenticate The Connector

1. Approve the connector when Claude opens the browser authorization page.
2. Confirm that the workspace or tenant shown in the browser is the right one.
3. Complete any consent screens.
4. Return to Claude and wait until it shows the connector as connected.

If you see a different tenant than expected, stop and reconnect before you start the interview.

4. Start The Conversation

Once the connector is connected, you can begin with:

start brand interview

You can also say:

I want to do a brand interview for <company name>.

Claude will then begin asking questions one at a time. The interview may use multiple turns, examples, follow-up questions, and option lists when that helps it collect better context.

5. How To Get The Best Results

The interview works best when you treat Claude like a thinking partner, not a form you are filling out.

Be concrete

• Give real examples instead of broad categories when you can.
• If Claude asks for a website, share the actual URL.
• If it asks for a feeling, story, audience, or proof point, answer with one specific instance instead of a slogan.

Use the options when they appear

Sometimes Claude will offer A/B/C choices and a recommendation.

• Pick the closest option if one fits.
• If none fit, answer in your own words.
• If you choose an option letter, Claude records the full meaning of that option, not just the letter.

Let the conversation breathe

• It is okay to ask Claude questions back.
• It is okay to explore a side idea before returning to the interview.
• If the conversation goes off track, just say back to the interview when you are ready to continue.

Ask Claude to think with you

Good prompts include:

• "Help me compare a few directions."
• "What would you recommend and why?"
• "Can you give me options and tell me which one you prefer?"
• "What am I missing?"
• "Can you summarize what we know so far?"

Review before finalizing

At the end, ask Claude to show the draft outputs that were actually created. Look for:

• the brand summary
• the design direction
• any questions or assumptions that still need edits
• the preview URL
• the generated Markdown files

If something is wrong, ask for edits before you approve the final output.

6. Review And Retrieve The Result

When the interview is complete, ask Claude to show the result it actually saved, where you can open it, and how to retrieve it later. A transcript or brand summary may be available; generated files, a completed DESIGN.md, or a preview are not guaranteed. Brand design work can be unavailable in some workspaces. Review the result and request an accessible copy if you cannot open it.

If the accessible result needs correction, ask for a revision and save the approved version. When ready to request design or website work, attach the approved content to one task and verify it opens after reload.

Troubleshooting

The connector says it is not connected

• Re-open the connector settings in Claude.
• Confirm you authorized the right connector URL.
• Sign out and reconnect if you used the wrong tenant email.

The interview feels too short

• Ask Claude to go deeper on the current topic.
• Share a concrete example, URL, or story.
• Ask for options if you are unsure how to answer.

Claude drifts away from the interview

• Say back to the interview.
• Then answer the question directly or ask Claude to restate it.

You want to revisit the final output later

• Ask for the saved transcript.
• Ask for the generated Markdown files.
• Ask for the preview URL again.

Suggested Prompt

If you want a simple starting message, send this in Claude:

Start the brand interview for <company name>. I want help thinking through the brand, and I’m happy to answer one question at a time.

If you want Claude to act more like a collaborator, send:

Start the brand interview. Ask me the questions one at a time, offer options when you have enough information, and help me think through the tradeoffs.

Last updated: 2026-11-02

Marketing

Use a Glance Agents task to request a campaign plan, brief, or draft. An agent may return copy in a board comment; that alone does not create a campaign email, schedule it, or send it. The available asset and sending workflows depend on your workspace. Review the exact output before an external action.

Back to main guide

Your Marketing Agents

The CEO can route a marketing request to the CMO. The CMO may delegate a campaign, copy, design, or QA step to a specialist when that agent and tool are available. Check the assignee and child tasks to see who owns each step. A role name on the board does not prove that a specific integration is connected.

Request And Review Campaign Work

For a complete worked example of questions, a corrected plan, review-only email drafts and a precise revision, watch the workshop example in Glance Agents. Its outputs are task-thread comments; check Campaigns separately before describing anything as a saved campaign asset.

To see agents plan email drafts and save them as drafts in Campaigns, watch Campaigns plan and revise email drafts.

1. Write the brief. Create a campaign brief on the board with the intended outcome, the audience, the offer, channels, and the date you need the work.
2. Give concrete facts. Keep unconfirmed dates, times and links marked as draft placeholders. Confirm every required detail before publishing, scheduling or sending.
3. Request assets after reviewing the plan. Ask for named draft assets, then confirm which version was actually saved. A board message can discuss a draft without creating a saved Campaigns asset.
4. Review before launch. Review claims, links, and approvals before launch. Scheduling, sending, and publishing need their own setup and checks; a confirmed plan is only the planning milestone.

Some campaigns use a staged pipeline to create and review assets. A board task does not automatically start it. Ask the agent or Glance team which workflow is configured, what it will produce, and where the saved assets will appear.

The Flow

1. Request a plan. State the audience, offer, outcome, channels, dates, and any existing source material. Ask the CMO to identify assumptions.
2. Review the brief. Correct the audience, claims, timing, or exclusions on the task before asset creation.
3. Confirm saved assets. Open the campaign's Assets tab or email template and check the version. A draft in a task comment is board-only.
4. Review quality and approval. Request the QA result for the exact version and use the campaign's approval path.
5. Schedule or publish separately. Confirm the sender, audience, consent, exclusions, time zone, and chosen version in the sending service. Check its schedule or send record afterward.

Copyable campaign request:

Help me prepare a campaign brief for [offer] for [audience], with
[intended outcome] and [date or undecided window]. Use [source links] for facts.
First ask the questions you need answered and identify who owns missing decisions.
This first step is questions only. Wait for my answers and a separate request
before preparing the plan or writing copy. Do not build, schedule, publish or send.

Webinar Campaign Templates

A configured webinar can have marketing and transactional email templates. Check the campaign's saved asset list and the provider workflow for the actual number, version, and schedule. A brief does not create these assets.

Glance Agents Integration

Open New Task, describe the campaign, and assign it to the CEO or the marketing owner shown in your workspace. Follow the delegated task and correct the brief there. A task may produce only a plan or copy draft. Ask where to review any saved asset before approving a send. See Work With Your Glance Agents.

Example: workshop emails, one decision at a time

Practice Studio is fictional. Replace its topic and audience with facts from your business. This example separates questions, a plan, drafts, and sending.

Ask questions before assigning work

Use your tenant assistant, Claude or ChatGPT to prepare the request. Submitting an assigned task can start an agent, so work through missing facts first.

Copy this example:

Practice Studio workshop email intake

I need help preparing emails for a live workshop about building a regular practice that fits an ordinary week. Our intended audience is people who have opted into relevant updates. Practice Studio is a fictional example.

Please start by asking questions. This first step is intake only: do not produce a plan, write email drafts or start implementation yet. Ask the most useful questions in a short group, explain why each answer matters, and let me answer “not decided” where necessary.

After the questions and answers have been saved and reviewed, I will separately ask for a plan. The eventual deliverables I have in mind are an invitation, one reminder and a follow-up outline, with a short explanation of what each message should do.

The workshop date, time, time zone, registration destination, price and replay policy are not confirmed. The sender also needs to be confirmed, along with who should be excluded from receiving messages. Do not borrow facts from another event or invent plausible values. Please ask who owns each missing decision and explain what depends on it.

Keep unresolved details in a separate decision list. Later writing should cover only facts we have confirmed; incomplete content must remain a draft. We will need a separate sending review before anything could be scheduled or sent.

For this intake, do not create a registration page, publish website changes, build live automation, schedule messages or send emails. The requested result now is a useful set of questions for me to answer.

Answer plainly. “Not decided” is useful: give the owner of that decision and keep it open. For example:

The date, time zone, registration destination and price are not decided.
Keep them open. Ask who should confirm them. Make no replay promise.
We also need to confirm the sender and who should not receive these emails.

Review the proposed plan

After the questions and answers have been saved, request the plan separately:

Use the brief and my saved answers to propose a plan for the invitation,
reminder and follow-up outline. Show the purpose of each message, the facts
it needs, and an owner for each open decision. Do not write the emails,
build automation, schedule messages or send anything yet.

Compare the plan with your request. Correct unsupported promises, missing decisions and extra work before moving on. A Plan-mode selection or a task status does not prove that the proposed work has been reviewed.

Request drafts from the reviewed brief

Put the complete brief, answers and reviewed plan on the Glance Agents task or attach a readable copy. Reopen it to check the right version is there before assigning draft work. See the Glance Agents guide for the task controls.

Use the attached reviewed brief and plan to draft the invitation and reminder,
and provide the follow-up outline. Keep unconfirmed date, time, price, sender
and link sections clearly unresolved. Do not invent event details. Show where
each result is saved and how I can reopen it. Do not schedule or send anything.

Read each result and ask for a specific correction, such as:

Make the invitation opening focus on a practice that fits an ordinary week.
Keep the unconfirmed date, price, sender and links unresolved. Show me the
revised version in the same saved location.

Reopen the revision. Confirm whether it is text on the task or a separate Campaigns asset. A writing response is not a schedule or send record. Follow the email review and sending checks below when the facts and copy are ready.

Watch Campaigns Plan And Revise Email Drafts

These two recordings use the fictional Practice Studio workshop and a campaign in Campaigns. Watch them in this order. In both, agents write a plan first, you approve it, and the emails are saved as drafts. A draft is a saved email that has not been sent. Nothing in either recording is sent or scheduled. The request also tells the agents not to read contacts.

Ask Agents To Plan Three Email Drafts

Use this when you want an invitation, a reminder and a follow-up planned for you.

Staging example: Ask agents from a campaign to plan an invitation, a reminder and a follow-up, answer their question, approve the plan and find the three saved drafts in Campaigns0:00 Why plan drafts in Campaigns0:10 Ask agents to plan drafts0:34 Answer the agent's question0:55 Plan mode and the plan1:37 Approve the plan1:52 Find the saved drafts2:19 What you have nowRead transcriptListen to audioThese are saved drafts only. Nothing is sent or scheduled. The request also tells the agents not to read contacts. The preview links on the saved drafts are not opened, so the wording of the emails is not shown. The blue note at the top of the plan task is written for the agents and is covered in the video. After Approve the mode button still reads Plan mode; the switch to Auto is explained but not shown on screen. An older request's card is hidden, and waits are labeled time jumps. The plan says the drafts use placeholders for date, time zone, sender and page address until you confirm them.Actual staging recording with narration and captions; three drafts are saved and nothing is sent or scheduled.

1. In Campaigns, open your campaign. In the box What should the emails do?, type what you want. The example asks for an invitation, a reminder and a follow-up, uses [DATE], [TIMEZONE], [SENDER] and [APPROVED_PAGE_URL] as blanks, and says not to send, schedule or read contacts.
2. Choose Ask agents to plan drafts. A card reads Review the plan in Glance Agents; open its link.
3. The plan task opens in Glance Agents. The blue note at the top is written for the agents, so you can ignore it. The CEO agent asks for the approved page and the audience. Choose I will provide the URL and audience and choose Submit answers.
4. The mode button already reads Plan mode. Campaigns chose it for you, so leave it alone.
5. The plan opens in the panel on the right. It says to create three review-only drafts and not to schedule or send anything. A card asks Do you accept this plan? with Reject and Approve. A comment is never approval. Reload the page: the plan is still waiting.
6. Choose Approve. The task switches to Auto by itself and the agents start the drafts. The mode button can keep reading Plan mode until you reload.
7. Go back to your campaign. The card first says Review the plan in Glance Agents; a short while later it changes to Saved in Campaigns and lists the invitation, the reminder and the follow-up, each at saved version 1. Reload to check that all three are still there.

The recording does not open the preview links, so it does not show the wording of the emails. The plan says the drafts use these blanks until you confirm the date, time zone, sender and page address. Open each draft to check, and fill them in before anything is ever sent. If the card stays on Review the plan or Preparing drafts for a long time, reload Campaigns, and if the plan task is still waiting, choose Approve on its plan card: nothing is saved before that. After the drafts are saved, the plan task may still show Blocked. Nothing more is needed from you.

Revise A Saved Invitation Through A New Request

Use this to change one saved email, such as a new subject line, while keeping the old version.

Staging example: Ask for a new subject line and main button on a saved invitation through a new request, approve the plan and check that the invitation is version 2 while version 1 is kept0:00 Why revise with a plan0:11 The saved invitation0:21 Ask for the change0:52 The new plan1:19 Approve the plan1:38 Find the new version2:24 What you have nowRead transcriptListen to audioNeeds a campaign that already has the three saved drafts from the previous lesson. Nothing is sent or scheduled. The request also tells the agents not to read contacts. The revised wording is not opened: the preview links are not clicked, so the new subject line and button appear only in the request text. After Approve the mode button may keep reading Plan mode until you reload; the video says so and does not show Auto. The blue note at the top of the plan task is for the agents and is covered. An older request's card is hidden, and two waits are labeled time jumps.Actual staging recording with narration and captions; the invitation becomes version 2 and nothing is sent or scheduled.

1. Start from a campaign that already has the three drafts above. Open it in Campaigns. Each draft reads saved version 1.
2. Use the same box to ask for the change. The example asks for the subject "A practical workshop for your next step" and the main button "See workshop details", to keep everything else the same and to send nothing. Choose Ask agents to plan drafts. A comment on an old task does not start this; use the form again.
3. A new card appears, Review the plan in Glance Agents. This is a new request, so the first card stays as it was. Open the link.
4. In the plan task the blue note is for the agents. This time the agents had no questions and the plan is already written. It changes only the invitation and carries the reminder and the follow-up forward exactly as they are.
5. Choose Approve on Do you accept this plan?. The mode button reads Plan mode and may keep reading it until you reload; the task switches to Auto by itself.
6. Go back to Campaigns. The new card goes from Review the plan to Preparing drafts and then Saved in Campaigns. In the example it took under a minute in real time. The invitation now reads saved version 2, and the reminder and the follow-up are still version 1.
7. Look at the card from the first request. It still lists the invitation at version 1, so your old version is kept. Reload Campaigns to check that both cards show the same.

A changed draft is saved as a new version. A version is a saved copy of the draft at one moment. The recording does not open the new invitation, so check the subject line and button yourself before relying on it, and confirm the sender, audience and timing in a separate review. Saving a draft is not scheduling or sending it.

Email details

Open Details beside an email in a campaign's Assets tab or an email template. The panel reports recorded uses, source, audience, trigger, timing, sending owner, approval, and version where known. It separates schedules from recorded sends. A schedule for an earlier version does not prove the selected version was sent.

A stored copy of an external-provider email does not control that provider's workflow. Open recorded workflow appears when its link was supplied. If the panel says Not verified or Not recorded, ask the owner to check the source or provider. An observed automation state may have changed since its observation date. Times show an explicit time zone.

Where an email draft lives

Copy in a task comment is board-only. A saved campaign email or template has its own asset, version, and Details view. A saved draft, a preview, an approval, a schedule, and a recorded send are separate states.

1. Give the brief. Ask for an email draft with the audience, intended outcome, the offer, and the sender name as a placeholder until it is confirmed.
2. Add required details. For a sample event, include the date, time, and checkout link as placeholders, plus any claims the team has approved.
3. Find the saved version. Review the reply on the board, then check whether a draft was actually saved as a Campaigns asset. A text response in the task is not the same as a saved version.
4. Review and send separately. Proofread subject, body, sender, links, and compliance details. Request changes in the thread. Sending or scheduling requires a separate workflow and the appropriate account setup; approving copy does not send it.

Editing campaign emails

Use Details to find the editing path for the exact email:

• Glance campaign email: use Copy change request and Open agents to request a revision. Review the resulting saved version. Editing a draft does not change an already scheduled version.
• Email template: use Edit template. Existing campaign assets or an external workflow are not rewritten by that edit.
• Source-managed email: give the agent or operator the campaign, email label, version, source link, and requested change. Review the synced version.
• External-provider email: ask the operator to update and verify the provider workflow. A stored Glance preview does not change what it sends.
• Unknown source: ask the operator to identify the owner and source first.

Copyable email request:

Please revise [campaign and email label], version [version]. Change [subject,
preview text, or body] to [exact request]. Tell me whether this is a saved
Glance asset, source-managed copy, or an external-provider email. Show me the
new saved version and its Details before anyone schedules or sends it.

Before a send, confirm the saved version, recipient audience, sending owner, sender address, consent and exclusions, timing, and required approval. Ask for a test or preview of the exact version that will send. The website review widget edits website content, not email campaigns.

How SMS Campaigns Work

SMS requires a configured provider, consent, suppression checks, an approved message, and a separate send action. Ask the operator which path is enabled for your workspace and verify the provider's delivery record.

How the Webinar Pipeline Works

A webinar may have separate planning, presentation, registration, promotion, live-event, and replay work. Ask for the actual asset list and owner of each step. A webinar brief or saved handoff is not proof that a presentation, registration page, reminder series, or replay has been published.

Brand Guidelines Enforcement

Give the agent your current brand source and ask it to cite the rule it used for a draft. Review factual claims, voice, accessibility, links, and audience fit yourself. A board comment alone does not show that a brand or QA check ran.

Quality Gate (QA Engineer)

For a saved email, request the QA result tied to its version. Check mobile rendering, link destinations, images-off content, accessibility, and provider delivery settings as relevant. If a check is unavailable, record that gap before approval.

What Needs Your Approval

The brief, final content, external publication, and each outbound send follow your workspace's approval policy. A task review card is not a send control.

What Happens Automatically

Only enabled workflows run. Ask for the trigger, owner, and last successful run when relying on automation, and check the saved asset or provider record.

Back to main guide

Last updated: 2026-10-25

Sales

Use a task in your Glance agents workspace to ask for sales research, a draft, or CRM follow-up. Which integrations and agents are available depends on your workspace. Do not assume a contact was updated or a message was sent because an agent described the plan in a comment.

Back to main guide

Ask For Sales Work

1. Open Glance Agents and create a New Task.
2. Name the intended outcome and identify the contact or segment using the records available in your workspace. Avoid pasting sensitive information into a task unless your team has approved that channel.
3. Assign the task to your sales owner or the CEO for routing.
4. Ask the agent to show the source record, proposed change, message draft, and next action in the task comments.
5. Review the result and use the task's Waiting on you card if one appears. Check the CRM or sending service separately for any claimed update or send.

Copyable request:

Review the new inquiries in our connected CRM. Summarize each lead's stated
interest and missing information with links to the source records. Draft a
follow-up for my review. Do not send messages or change deal stages until I
approve the exact action.

CRM And Messaging

A connected CRM can provide contacts and deal context. The exact provider, fields, and write permissions vary by workspace. Ask the agent which record it read and what it changed; then verify the result in the CRM. A task comment is not a CRM audit record.

For email or text outreach, review the exact recipient, channel, sender, message version, consent or suppression status, timing, and approval path. Confirm the send in the sending service. A draft or task approval does not prove delivery. If the provider is disconnected or a guard refuses a send, resolve that state with your operator before retrying.

Approval Workflows

Use the review card or your team's stated approval process for the proposed action. If you need a different draft, choose Needs changes and state the specific correction. A review decision can close a task without sending a message; check the delivery record.

What Happens Automatically

Only workflows configured for your workspace can run. To confirm one is active, ask for its trigger, owner, last successful run, and provider record. If those are unavailable, treat the task as a request for manual review.

Back to main guide

Last updated: 2026-10-25

Programs

Program tasks can help staff organize intake, preparation, and logistics when the relevant tools are enabled. Medical screening and participant decisions require the clinical and human review process set by your organization. A draft recommendation is never an admission or medical decision.

Back to main guide

Request Program Support

1. Create a task in Glance Agents and assign it to your program owner or the CEO for routing.
2. State the requested outcome and the source system that holds the record. Use a record link or approved identifier; keep sensitive medical details in your approved clinical system.
3. Ask for a factual summary with source links, missing information, and a proposed next step.
4. Review the task and verify any claimed update in the source system.

Copyable request:

Review the preparation status for the upcoming program using our connected
records. List incomplete logistics items and the source for each. Draft a
participant reminder for staff review. Do not send it or make a screening
decision.

The Onboarding Flow

A typical process may include an application, staff screening, clinical review where needed, agreement, and preparation. Your workspace may support only part of this sequence. Confirm the configured form, CRM, agreement service, and sending service with your operator before relying on automation.

Integrations

Connected services appear in your workspace's integration settings. A service name in a task or guide does not prove it is connected or has permission to write. For a claimed record change, open the record in that service.

What Needs Your Approval

Your organization defines who may approve admission, clinical decisions, agreements, and participant communications. Keep that decision with the authorized person. If a task is blocked, read its latest comment and follow the stated handoff; do not infer that an agent approved a participant.

A Note on Safety

Do not put medical details into an ordinary marketing or sales task. Use the approved clinical workflow and ask your program lead when the correct path is unclear.

Back to main guide

Last updated: 2026-11-02

Request Changes On Your Website

The review widget lets you request a change against a review copy of your site. Available actions depend on the site and workspace. Follow the current panel instructions; screenshots and older recordings may show a different version. A submitted request, preview, review decision, and published page are separate states.

Back to main guide

Before You Start

• Sign in to the workspace that owns the site.
• Open the review copy for the correct site and check the page before sending a request.
• If a needed action is not offered or the panel declines the request, use a task or contact the Glance team.

Request And Review A Change

This staging recording shows how to prepare a specific wording request. It stops before adding or sending the request because the existing batch needs attention.

Staging example: Open Request changes, select a heading, and prepare a specific wording request on a review copy0:00 Open Request changes on the review copy0:04 Select the main heading0:08 Describe the requested wording · idle cut0:24 Leave the request unsentRead transcriptListen to audioThe existing batch needs attention, so the request is left unsent and unadded. No applied change, finished preview, acceptance or live publication is shown. Earlier test copy is visibly hidden. The requested wording is shown in the draft request box; no applied heading is shown. An inspection wait is cut.Actual heading selection and an unsent wording request; Austin narration and captions.

For the fictional workshop, the request is:

Change the main heading to “Build a practice that fits your week”. Keep the supporting paragraph, Get Started button and layout unchanged. Please prepare a preview for review before any live update.

1. Check Review copy · Not live, then choose Request changes if offered.
2. Select the heading and describe the exact wording you want. Name the parts that should stay unchanged.
3. Read the current batch status before adding or sending anything. If it needs attention, follow the existing thread or ask the owner for the next step. Avoid overlapping the same change with another request.

The clip demonstrates preparation only. It does not show a submitted request, an applied change, a finished preview, acceptance or publication. The following checklist covers those separate stages.

1. Open the site's review copy using the link or action available in your workspace.
2. Select or describe the page area if the widget offers that action. State the exact result you want and include source links for factual changes.
3. Submit the request using the current panel control. A receipt confirms the request was recorded; it does not prove a change was made.
4. If the team asks a question, answer in the same request thread. If the request is declined, follow the explanation or use a task.
5. When a preview is available, inspect the affected page and request corrections before approving it.
6. After approval, follow Check the live result. Approval alone is not proof that production changed.

If the panel offers a Looks good — accept action, use it only after reviewing the exact preview. If the panel shows another action or wording, follow the current interface.

Watch A Website Change From Request To Live

These three recordings continue the fictional Practice Studio workshop page from Work With Your Glance Agents, where the plan is approved and the website build is waiting. Watch them in this order. A request, a preview, an accepted preview and a task marked Done are separate states, and the live page is the one that counts.

Request A Page Correction

Use the review widget for a small fix on a page you can see, such as a button label. You must be signed in to the website app as a member of the workspace, which is separate from the Glance board. Without it the widget offers only Sign in to request changes. The site also allows one active review at a time, so the slot must be free. This request is what starts the waiting Website build task.

Staging example: Request a page correction in the review widget, link it to the approved website task and send it once0:00 Why use the review widget0:15 Describe the change0:30 Add the request0:35 Link the approved work0:56 Send once1:12 The preview is ready1:23 What you have nowRead transcriptListen to audioThe clip opens on a page-not-found screen because the page is not built yet. The preview arrives much later (about 40 minutes in this example). The last part of the clip shows the panel at Preview ready and the new button on the review copy. Nothing is live. The pasted work link is truncated in its field and the line saying that publishing needs a separate acceptance is cut off at the bottom of the panel.Actual staging recording with narration and captions; the preview arrives much later and nothing is live.

1. Open the practice page on the review copy at exactly /live/november-workshop (/practice/... is a "not found" page). The chip at the top left reads Review copy · Not live. At first the page says "This page could not be found". That is expected: the page has not been built yet.
2. The panel may still show a red Failed and Try again from an earlier request. That is not your request, so do not choose Try again. A new request starts fresh.
3. Choose Request changes, click the heading, type the correction in What should change? and choose Add. The toolbar then shows Send with 1 unsent request.

On the approved fictional practice page at /live/november-workshop only, change the primary label to “See workshop details.” Preserve the rest of the page. Link this request to the approved implementation task and return a staging preview. Do not publish.

1. Scroll inside the panel to Approved work link (optional). On your Glance board open B - Website build, copy its address from the browser and paste it, then choose Check link. The line below reads Checked: B - Website build. It names the task, not a task number. The next line, which may be cut off at the bottom of the panel, says the link ties the approved work and that publishing still needs your separate acceptance.
2. Choose Send once. The panel changes from the old Failed to Working on it, and the thread says the review is connected to the existing approved task. The website task wakes within seconds. A long note for the agents may appear in the panel's thread. It is not for you; ignore it.
3. The preview arrives later, when Glance's regular check picks up the finished work. In this example it took about 40 minutes, longer than the usual 30, and waking the agent does not hurry it. The chip can say Working on it or Needs attention meanwhile. Do not call it ready until the panel says Preview ready.
4. When it does, the page is built and shows two "See workshop details" buttons, and a View your review copy link appears under the status.

Working on it means the request was received and work started. It is not the result. Your live page has not changed.

Review The Preview

Done is not the same as live. Check the preview before you say yes.

Staging example: Open the preview, read it on desktop and phone-sized views and read the review choices without accepting0:00 Done is not live0:09 Preview ready0:17 Open the review copy0:25 Scroll the whole page0:33 Phone-sized view0:45 Back on the preview page0:51 An older line may say building1:00 The three choices1:21 A preview onlyRead transcriptListen to audioNothing is accepted or published in this clip; accepting is shown in the next lesson. An older progress line may still say the preview is building; the status at the top is the current one. The phone-sized view is shown enlarged.Actual staging recording with narration and captions; the preview is only reviewed, nothing is accepted.

1. Start where the previous recording ended: the panel reads Preview ready, and the thread shows how long ago you sent the request (about 41 minutes in the example).
2. Choose View your review copy. It opens the home page of your review copy in a new tab. Then go to /live/november-workshop. The review panel is not shown on that copy.
3. Scroll the whole page, including the schedule and the Explore the example day section, then back up.
4. Check a phone-sized view, about 450 px wide. The schedule cards stack in one column.
5. Go back to the page with the panel and scroll it to read the thread. A long note for the agents may be there; ignore it. An older line may still say the preview deployment is building. The status at the top, Preview ready, is the current one.
6. At the bottom are three choices: Looks good — accept, Something's off — reopen and Request more changes. A notice such as Page changed since you commented may sit above them. If a correction is needed, add a concrete comment or choose Request more changes. Do not accept in this recording.
7. Reload. The panel still reads Preview ready.

You are looking at a preview only, and your live website has not changed. Task Done is not the same as live, and a comment is not approval. Accepting a preview is its own decision, shown next.

Accept The Preview And Check The Live Page

Use accepting only when you want the page live. In this fictional practice site there is no separate publish button: Looks good — accept in the review panel is what puts the page on the live site. Approving a plan or finishing a task never does.

Staging example: Accept a reviewed preview, check the live page, mark the website task Done and read the parent task's closing note0:00 Publishing is its own decision0:10 The live address today0:16 The reviewed preview0:24 The choices at the bottom0:40 Click Looks good, accept0:52 Check the live page1:03 Set the task to Done1:13 The closing noteRead transcriptListen to audioIn this fictional practice site, accepting the preview is what puts the page on the live site; there is no separate publish step. The page appears after a short wait shown as a labeled time jump. Nothing in the product undoes an accept; a later change goes through a preview again. The closing note may still call the preview unpublished; the live page is what counts.Actual staging recording with narration and captions; accepting puts this practice page live.

1. Open the live address of the practice page (/live/november-workshop). It shows "This page could not be found."
2. Open the reviewed preview. The panel reads Preview ready. Scroll the panel to the three choices and choose Looks good — accept once.
3. The two large buttons fade and the thread says "This review is closed and can no longer receive replies". The Accepted text also says to mark the website item done on your Glance board.
4. Wait about a minute, then open the live address again. In the example the page answered about 45 seconds after the click. If you still see "not found", wait and reload. The live address then shows the workshop page without the review panel. Scroll it, reload it and check a phone-sized view, and open a couple of other pages of your site to confirm they look as before.
5. One last step: open the website task on your Glance board, choose Change status and choose Done. About 13 seconds later the CEO agent closes the main task, and its header shows a green check. That check means Done; the header shows no word.
6. The CEO's closing note may still say the preview "remains unpublished". It was written after the page went live and is out of date. Open the live page to check.
7. Nothing in the product undoes an accept for you. To change the page again, request a new change in the review widget with the same steps as above. It goes through a preview again before it goes live. If you need help, ask your Glance team.

Closing a task never publishes. Accepting the preview does. The live page is what counts.

Check The Live Result

1. Ask the request owner or workspace team who performs production publication and where its result will appear. If the panel does not show a publication result, keep following the same request thread.
2. When publication is reported, open the live page at the published address, reload it, and compare the changed page with the preview you approved. Check its links and form if they were part of the change.
3. If the live page differs, the destination is unclear, or no publication result is available, reply on the request with its link and what you see. You can also contact team@mail.getglance.com.

For work requested in Glance Agents, keep this discussion on the original task. A completed task or accepted preview does not replace checking the live page.

If Something Looks Wrong

• Do not approve a preview that misses the request. Ask for a specific correction in the request thread.
• If the panel says the request is accepted but the live page has not changed, contact team@mail.getglance.com with the request link.
• If the request is blocked or unsupported, ask for the task-based or operator-assisted path.

Which Channel Do I Use? compares the review widget, Glance Agents, and Telegram. See Marketing for campaign and email work.

Last updated: 2026-11-02

Work With Your Glance Agents

Use Glance Agents to request a website change, campaign work, research, or another clear deliverable. What an agent can do depends on the workspace, permissions, and connected tools. A task assignment is a request; it does not guarantee a start time, saved asset, publication, or send.

Back to main guide

Before You Start

• Sign in at agents.getglance.com with your invited account.
• Prepare the brief before assigning work. If New Task shows Auto mode, open that menu, choose Plan mode, and check that the closed button now reads Plan mode before selecting Create Task when you want a proposal first. If the picker is absent, prepare and approve the brief in Claude or your tenant assistant before submitting an assigned task. A sentence such as “plan only” does not enforce a plan-only boundary.
• Save any interview outputs you intend to use. Transfer the approved content through an attachment or other tenant-accessible method, then reopen it after reloading the task. A filename or server path is not proof that you or the assigned agent can read it.
• If the output cannot be transferred and read back, ask the Glance team for an accessible copy. Keep this manual handoff until automated transfer is demonstrated in your workspace.

Projects And Tasks

Use a project to group related work and a task for one requested deliverable.

Try the fictional workshop example

Give related work a clear project name. For this practice example, copy:

Practice Studio workshop

Choose Add Project, enter the name, then choose Create project. Open the project to check its task list before adding your detailed request. Creating a project does not start agent work.

Staging example: Create the fictional Practice Studio workshop project and open its task list0:00 Create a project0:12 Open its task list · inspection wait removedRead transcriptListen to audioProject creation and opening its task list only. Reload, task creation, agent work, plan approval and a complete workflow are not shown.Staging example with Austin narration and captions; project creation and opening its task list.

1. Open the project for the work, or select/create one if that option is available.
2. Create one task with a clear result, relevant source links, required inputs, deadline if relevant, and review criteria.
3. Assign it to the owner shown in your workspace. CEO routing is available in some workspaces; verify the assignee on the task.
4. Reuse the existing task when correcting the same deliverable. Create another task only for a separate outcome.
5. Reload the task and confirm its description, project, assignee, attachments, and comments are present.

See Request work from interviews for transferring approved source material.

Request A Task

The fictional Practice Studio example shows a detailed website request being created in its project. The brief asks for questions first, lists missing facts and decision owners, and requests a preview before any later website review.

Staging example: Create one detailed website intake in its project, confirm Plan mode before saving, expand the saved brief and check current ownership0:00 Create a detailed task in the project0:08 Confirm Plan before Create0:18 Reopen the saved request0:24 Expand the saved brief0:37 Check current owner and blocked statusRead transcriptListen to audioThis is an intake, not a website build or publication. The task initially appears unassigned; Site Builder later responds. Check the current owner and latest status. Questions and a blocked status remain visible. Typing and waiting cuts are labeled.Actual staging recording with Austin narration, captions and a saved-request check.

Finish the brief before Create Task. Check that the closed mode control reads Plan mode when you want a proposal first. Reopen the task, use Show more to read the complete request, and check Properties for the current assignee, project and status.

In this example, the saved task initially showed Unassigned and Site Builder later responded. An initial unassigned label does not guarantee that no agent will pick up the work. Read the latest response before adding another request.

1. Open the task board and choose New Task.
2. If you want a proposal before work begins and see Auto mode, open its menu, choose Plan mode, and check that the closed button reads Plan mode before selecting Create Task. If the picker is absent, prepare and approve your brief in Claude or your tenant assistant first, then submit the assigned request when you are ready for work to start. The exact approval control and what starts implementation still need verification in your workspace.
3. Write the result you need, not just an activity. Include the audience, source links, attached interview material, output format, and what needs your review.
4. Assign the owner shown in your workspace. Check the task after it is saved.
5. Follow comments and any child tasks. A handoff or status change does not prove the deliverable is complete.
6. Open the actual output. Request corrections in the task thread and reload to confirm the change.
7. Treat approval, task completion, publication, scheduling, and sending as separate steps. Verify the external result in its destination.

Copyable website request:

Prepare a plan for [website/page deliverable] for [audience]. Use the attached approved interview outputs and [source links]. Identify missing facts before drafting. Deliver [specific pages/content] as a reviewable draft or preview. Do not publish. Tell me what was saved and where I can open it.

For webinar, campaign, and email prompts, see Onboarding. For campaign asset and sending states, see Marketing.

Create A Task From An Approved Brief

Before submitting, read the complete brief and correct it. Include the page or output you mean, who it is for, what should change, what should stay the same, and how you will check the result. Keep missing dates, prices, links and sender details explicit.

Saving a request, receiving questions, reviewing a plan, and authorizing drafts are different steps. The recordings below follow the workshop email example through those steps on one task.

Questions And Plan Reviews

Answer the questions on the existing task. State the facts you know. For anything undecided, name the decision owner rather than inventing an answer.

Staging example: Read saved intake questions, answer them once on the same task, and check the saved summary0:00 Read Site Builder’s questions0:08 Answer with facts and decision owners0:25 Send once on the same task0:34 Check the saved intake summaryRead transcriptListen to audioThis example uses a normal task reply, which wakes the assigned agent. It does not show a question card, plan approval, email drafts or a complete workflow. Typing and waiting cuts are labeled.Actual questions, a reply and its saved intake summary; Austin narration and captions.

The example uses a normal task reply, which wakes the assigned agent. It does not submit a question card or approve a plan. The saved summary separates confirmed answers from unresolved decisions.

Request a plan, then correct it before drafting. In the example, the reminder should help registered attendees with event logistics. The first plan instead proposes another registration pitch, so the reply requests that one correction.

Staging example: Request a plan only, correct its reminder audience, and review the revised plan in the task thread0:00 Ask for a plan only0:13 Read the proposed sequence0:18 Request one correction0:29 Check the revised plan and storageRead transcriptListen to audioThe plan is text in the task thread. A separate Plan document or approval card is not shown. Drafting and sending are not shown in this clip. Typing and waiting cuts are labeled.Actual plan request, correction and revised task-thread plan; Austin narration and captions.

This plan is saved as text in the task thread. Read its sequence, placeholders, decision owners and storage location. Ask for the corrected version before authorizing the next step.

Authorize the specific next step. The next example selects Auto mode after plan review and explicitly requests review-only drafts. The invitation, registered-attendee reminder and follow-up outline stay marked NOT READY TO SEND. A later reply quotes one replacement opening and checks the saved revision.

Staging example: Request review-only invitation and reminder drafts and a follow-up outline, then check an exact invitation revision0:00 Authorize review-only drafting in a comment0:15 Read the three draft texts0:29 Request one precise copy revision0:40 Check the saved openingRead transcriptListen to audioThe drafts are task-thread comments, not Campaigns assets or sent emails. The follow-up is an outline. Approval is an explicit reply in this example; no separate approval card is shown. Missing facts remain placeholders. Typing and waiting cuts are labeled.Actual review-only drafts and a precise saved revision; Austin narration and captions.

These outputs are task-thread comments. They are not saved Campaigns assets or sent emails. Missing facts and sending reviews remain outstanding. See Marketing for checking the actual destination before scheduling or sending.

If your task shows a question card, complete that card and use its submit button, often Submit answers. This keeps your answer attached to the question. If there is no question card, use the existing task thread and state exactly what the agent should do next.

If a Plan tab is available, open the saved proposal before reviewing it. A comment describing a plan is different from a saved plan awaiting approval. If there is no saved proposal or review card, ask the owner to provide one before starting work.

When a plan review card appears, use the approval button shown on that card only when you are ready for implementation to begin. To change the proposal, choose Revise… if offered, enter the change, and choose Send revision. Review the updated plan before approving it. A normal comment or status change is not the same as accepting that plan review.

The exact cards depend on your workspace and the agent's response. If these controls are missing, prepare and approve the brief in Claude or your tenant assistant first, then submit the implementation request when you are ready. Approval does not prove that publication or sending is complete. Keep any “do not publish/send” restrictions explicit in your brief, and check the external result separately.

Use Which decision am I making? to distinguish approving source material, accepting a saved plan, reviewing a result, and checking publication.

Board Reference

The controls available depend on your workspace and permissions. Ask an administrator about missing areas.

Check task ownership and the roster view.

Staging example: Read the recorded task questions and Properties, then inspect the agent roster filters0:00 Read the saved questions0:06 Check task Properties0:12 Inspect the Active roster0:18 Inspect Paused agents0:22 Inspect Error state0:26 Return to AllRead transcriptListen to audioTask and roster views are assembled from separate chronological takes, with waits shortened. The Active filter narrows the roster and is not execution proof. No resume or settings change is shown; the recording does not establish other automated actions.Recorded task Properties and roster filters from separate chronological takes; Austin narration and captions.

Read the task's current assignee, project and status in Properties. An Active roster filter is not proof that an agent is running your task. Read the task's latest reply or run status before treating it as in progress. This reference shows no resume or settings change.

Find existing work before requesting more.

Staging example: Filter and search task rows, read a saved draft in a separate task view, then sort and open the workshop project0:00 Filter and search tasks0:12 Read saved draft text0:32 Sort Projects by Updated0:38 Open the workshop projectRead transcriptListen to audioSeparate recorded scenes show task search, an existing task conversation and Projects. Opening a task from the search results is not shown. Drafts are shown as task-thread text with unresolved placeholders; Campaigns storage and sending are not shown. Waits are shortened.Task filtering/search, a separate saved task conversation and the project's Updated list; Austin narration and captions.

The separate scenes show task filtering/search, a saved task-thread draft and the project's Updated list. Check the matching title and actual saved text before following up. Opening a task from the search results is not shown. Drafts in a task comment still need separate Campaigns storage and sending checks.

Advanced Areas (Read Only)

These sections help you understand records. Ask an administrator before changing configuration or access.

• Agents and availability: an agent roster may show whether an agent is paused. A paused agent may not take new work.
• Runs and activity: review the latest run/error and record history. A successful run can still produce an incomplete output.
• Costs and budgets: displayed usage or limits do not guarantee a particular task can run.
• Routines: check the owner, cadence, connected tools, and actual run history before relying on automation.
• Settings: membership, credentials, budgets, and runtime settings require administrator access.

If Something Looks Wrong

• No response: check assignee, latest comment, paused state, and any named blocker before creating a duplicate.
• The output is wrong: request a specific correction on the task and confirm the revised version is saved.
• You cannot open an attachment or preview: contact team@mail.getglance.com with the task link and what you can access.
• The task is done but nothing is live or sent: check the separate publication, schedule, or sending record.

Do not include passwords or API keys in a task. When contacting support, include the task link, expected result, and visible status.

Watch A Plan-First Website Task

These three recordings follow one fictional Practice Studio workshop-page task from choosing Plan mode to approving a plan. Watch them in this order. A comment, an answer to a question, an approved plan, a preview and a live page are different things, and each recording says which one you are looking at. The review-widget steps that come next are in Request Website Changes.

Choose Plan Mode And Create The Task

Use this when a page has many choices and you want to review a plan before anything changes. Plan mode makes the agent ask questions and write a plan first. Auto mode goes ahead, for example to fix a phone number. Ask mode only answers, for example which pages mention refunds.

Staging example: Choose Plan mode, pick the lead agent, create a website task, answer its question card and find the saved plan awaiting your decision0:00 Why use Plan mode0:13 The mode menu0:49 Choose Plan mode0:55 Pick who the task is for1:07 Create the task1:14 Open the new task1:22 The agent asks four questions1:28 Answer the questions1:59 Answers submitted2:05 The plan arrives2:25 Reload and check2:32 What you have nowRead transcriptListen to audioStops at the saved plan awaiting a decision: Approve and Reject are not clicked and nothing is changed or published. The mode menu is held on screen while its three choices are explained. The wait while the plan is written is a labeled time jump. The reload check is described in the written steps and is not clearly visible.Actual staging recording with narration and captions; stops at a saved plan awaiting a decision.

1. Open your workspace and the practice project, then choose New Task. The mode button reads Auto mode.
2. Open the mode button and choose Plan mode with the mouse. Typing a mode word does not set it. Check that the closed button now reads Plan mode.
3. Choose Assignee, type CEO and pick the CEO agent, the lead agent on your Glance Agents team. Pick the assignee before you create the task.
4. Type a short title (it is required), paste the request below into the description and choose Create Task.

Plan an isolated practice workshop information page for the Practice Studio November Workshop project. Ask me for the approved source page, fictional date/timezone, page path and review criteria before anything is changed. Preserve all existing pages. No contact access, registration integration, email sending or publication. Show me the proposed plan for review.

1. Open the new task. Your request is the first message. About ten seconds later a card named Questions appears. For each question choose Other, type your answer and choose Next. On the last card choose Submit answers. The example answers are: source page /; Saturday 21 November 2026 in America/New_York; page path /live/november-workshop; and review checks that the page renders, the main action reads "See workshop details" and no existing page changes. When your answer starts with /, a menu of skills opens under the box. You do not need any of them: finish typing, ignore the menu and choose Next.
2. After Answers submitted, the conversation shows your answers as one message and the agent keeps working. In the example the plan took about 25 seconds. Sometimes the agent first posts a short No reply notice; wait a moment, and if no plan card appears, send the word continue in the task.
3. The plan arrives as a Plan, rev 1 card, and the agent says it is saved and awaiting your review. A card asks Do you accept this plan? with Reject and Approve. Do not choose either yet. The website is unchanged.

A saved plan is a document on the task, not a published page. An answer or a comment is not approval. Only Approve on the plan card approves.

Revise The Plan In The Same Task

Use this when the plan is not quite right, for example the wrong button label. Reply in the same task instead of starting a new one.

Staging example: Hide the approval card, reply in the same task, and check the saved second plan revision0:00 Why reply instead of starting over0:12 Hide the approval card0:20 Type and send the reply0:29 The agent starts working0:37 A revised plan arrives0:52 Check the new plan tab1:02 Approve the new revisionRead transcriptListen to audioNothing is approved or published. The reply is a normal task message and does not approve the plan. Approving the new revision is shown in the next lesson.Actual staging recording with narration and captions; the plan is revised and nothing is approved or published.

1. On the task with the waiting plan card, choose the small x on the card. It only hides the card on your screen; nothing is rejected. A message box appears, still reading Plan mode.
2. Paste your reply and choose Send:

Please revise the plan: make the main action “View the workshop schedule” and keep it informational. Keep the same task and project; do not create duplicate work or publish.

1. The first approval card disappears and your reply shows in the thread. A reply is a normal message in the task and does not approve anything.
2. About ten seconds later the agent confirms in one line that it will revise the existing plan and posts a new card, Plan, rev 2. No question card appears this time. The plan tab reads Revision 2; scroll it to find the new button label. The product does not show the earlier revision beside it.
3. Reload the task. It still shows Revision 2, your reply and one waiting approval card, and there is still one task. Stop here.

The new plan version is saved and the earlier card has expired, so you approve the new one. Nothing is published.

Approve The Plan And Follow The Work

Use this when the plan looks right. Approve is the one click that starts the work.

Staging example: Approve the second plan revision and follow the tasks that the approval creates0:00 Why approve the plan0:12 Click Approve0:17 The task starts working0:22 Auto mode after a reload0:30 Delegation appears0:39 Marketing adds its own tasks0:48 Nothing is complete yet0:54 The copy tasks finish1:04 Marketing production is done1:11 The website build is still waiting1:23 Blocked after a reload1:38 Where things standRead transcriptListen to audioThe website build is left waiting; a review-widget request in a later lesson is what connects it. The main task reads Blocked because it is waiting on the website task. Nothing is live. Waits are labeled time jumps.Actual staging recording with narration and captions; labeled waits, website build left waiting and nothing live.

1. Open the task and check that the card reads Plan, rev 2. Approve only the card for the revision you reviewed.
2. Choose Approve on Do you accept this plan?. The card disappears, the conversation shows Approved plan and a toast says Request confirmed. The task starts working.
3. The mode button may still read Plan mode for a while. After you reload, it reads Auto mode: approving switched the task to Auto for you.
4. Open the Tasks tab. Approval created two tasks under this one: Marketing production, in progress, and Website build, waiting to start. About 30 seconds later Marketing adds two tasks of its own, landing and thank-you copy and an informational email sequence (drafts for later; nothing is sent), and the count reads 0 of 4 complete.
5. Within about 90 seconds in this example the copy tasks finish and the count reaches 3 of 4. A small toast such as CMO created ... or a cancelled-run notice may appear lower left; they are only notices.
6. Website build stays waiting. It does not start on its own: it starts when you ask for the website change in the website review widget and link this task to that request. Reload the main task and its Properties tab reads Blocked in red. Here, Blocked means the main task is waiting on the website task; nothing is broken. Your next action is the review-widget request in Request Website Changes. Do not open the widget yet.

At the end, the task is in Auto mode, the marketing work is done, the website work is waiting and nothing is live. Approving a plan does not publish a page, and a plan comment is not the same as a saved plan awaiting approval.

Take A Website Task From Plan To Live

Keep the brief, questions, preview, corrections and release result on one task. This checklist explains what to ask for and what to check; it does not mean every step is automated in your workspace. If a control is missing, ask the owner for the supported next action instead of creating the same request again.

The short recordings above cover only the actions named in their captions. They do not demonstrate this entire sequence.

1. Prepare The Brief And Interview Outputs

Start with the result you want, even if you are unsure how to describe it. You can prepare the brief with your tenant assistant, Claude or ChatGPT:

Help me plan [the result I want] for [audience]. Ask one clarifying question at a time. Use [approved interview outputs and source material]. Show me the proposed work, missing facts, what I will review and how we will check success. Wait for me to approve the brief before assigning implementation.

Answer with facts and examples. Keep unknown dates, prices, links or sender details marked as questions. Review the complete brief and correct it before using it.

For a Claw Interview, save the complete approved output and transfer it into the work request by pasting it, attaching it or providing a document both you and the assigned agent can open. Reopen the source after reloading the task and ask the agent to repeat a specific fact from it. A filename or server path alone does not prove access. Keep this manual handoff until automated transfer is demonstrated in your workspace; completing an interview alone is not proof that a website, webinar or campaign was created. See Onboarding.

2. Save One Task In The Right Project

Check for an existing task before creating one. Use the project for this work and include the approved brief, page address, audience, requested result and success checks.

When New Task offers a mode menu and you want a proposal first, choose Plan mode and check the closed mode button before selecting Create Task. If that choice is absent, finish and approve the brief before assigning implementation. A sentence such as “plan only” in an ordinary assigned request does not enforce a planning boundary.

Reload the saved task. Check its project, owner, description and readable attachments. Keep later questions and corrections on this request; create another task only for a different deliverable.

3. Answer Questions On The Existing Request

Read the latest question. If the task provides a question card with choices or a text field, use that card's own response control. Otherwise, reply in the same task thread. Check that the answer saved, then ask which missing facts still block the plan, a draft or publication.

For the question in this task, my answer is [approved fact or decision]. [This detail] is still unknown. Please update the same plan or draft, keep other approved facts unchanged and tell me what remains blocked. Do not create a second request.

Do not approve invented facts to keep work moving.

4. Approve The Plan Before Starting Implementation

Read the current saved proposal or approved brief. Check the scope, source material, missing facts, deliverables and what you will review. Request revisions before approving it.

Use a native plan-review control only when it is actually offered and you understand what it starts. A plan described in a comment, a saved proposal and an accepted plan review are different records. If there is no plan-review control, ask the owner to explain the supported handoff from the approved brief to implementation and record it on the existing request.

When you are ready to start the agreed work, make the boundary clear:

Use [the approved plan or brief version] to implement only [the agreed deliverable]. Keep the current live site unchanged while I review. If a required fact is missing, ask here and wait. Return the saved output, the actual staging preview URL, what changed and the QA result. Do not publish yet.

Approving a plan is not proof that implementation has finished, a site is published or an email was sent.

5. Follow Execution And Ask For The Actual Preview

Check the owner, latest update, status and any linked child task. Assignment does not prove that work started or finished. If work is blocked, answer the named question or ask the owner what is needed. If an agent is paused, ask your workspace team for help; duplicating or reassigning the request can create overlapping work.

For a website change, the delivery must include a staging preview you can actually open for the current revision. If the CTO owns the work and has not supplied it, ask the CTO on that task:

Please post the actual working staging preview URL for this revision, the exact pages to check, what changed and the QA result, including any untested checks. Include the tested version or commit if it is available, and keep the PR link separate. If the preview is missing or inaccessible, explain the blocker and use the existing owner/task to obtain it. Keep the live site unchanged while I review. Do not include credentials or access tokens in a link.

A PR is the source-review record. A screenshot, guessed address, promise of a preview or link to the unchanged live site does not replace an accessible preview. If the preview is missing, inaccessible or untested, keep the review waiting on that blocker; do not call the change ready to publish. If a team member prepares preview access for you, ask them to record that assistance and the actual link on the task.

6. Check The Preview And Request Corrections

Open the exact preview on a computer and phone. Read the changed copy, try the navigation and links, and check the requested behavior. Reload before accepting and confirm you are still reviewing the intended version. Compare it with the live page, which should retain its previous version before publication.

For a form, test validation and use only an agreed controlled QA destination for a submission. Verify who actually received it; a success message alone does not prove inbox or CRM delivery.

Give one specific correction in the same task or the review widget associated with that request:

On [the preview URL], change [current wording or behavior] to [desired result]. Keep [approved parts] unchanged. Return the updated preview, identify the version I should review and explain what changed. Do not publish yet.

Reopen and reload the revised preview. Check the correction and nearby content. An acknowledgment or a new status is not proof that the change was made.

7. Review The Exact Result And Publication Decision

Use the result's review control when available and confirm it refers to the version you inspected. If the revision changes afterward, review the relevant changes again. A generic Looks good confirmation can have a different purpose from accepting a plan or publishing a site; read what the actual control asks you to decide.

Keep these decisions separate:

• Approving source material means those facts can be used.
• Accepting a plan agrees to the proposed work and its implementation handoff.
• Reviewing a result accepts the exact saved output or preview you inspected.
• Marking a task Done records its board state.
• Authorizing publication permits the product's release action for the stated scope.

If the next action is unclear, ask what it will do before choosing it. A normal approval comment must not be treated as a substitute for a required publication confirmation.

8. Follow The Merge And Deployment Handoff

For code changes, merge means incorporating the approved work into the source used for release. Deployment makes a version available at its destination. A preview deployment and a production deployment serve different purposes, and a merge alone does not prove the public site is live.

Ask the owner to record the reviewed revision, passing checks, merge result when applicable, intended production destination and who performs publication. Tenants do not need to open a code tool unless their actual workflow requires it. If a team member merges or deploys on your behalf, keep that operator-assisted handoff on the task.

Use the verified publication control offered in your workspace. If the product asks for a specific literal confirmation or command, follow that exact product-provided confirmation and its displayed scope; do not substitute a planning message or generic approval. If the control is unavailable or its effect is unclear, ask the Glance team to complete the supported handoff. Do not put secrets or credential-bearing deployment instructions in a task comment.

If checks fail, the revision changes or the publication result is uncertain, keep the release waiting for clarification. Do not start a duplicate deployment to obtain a clearer answer.

9. Verify The Live Page And Save The Outcome

After publication is reported, ask for the publication/deployment result and exact live page address. Open it, reload and compare it with the approved preview. Check links, navigation, phone layout and the agreed form behavior or controlled delivery. Confirm unrelated live content remains intact.

If the page differs, reply on the same task with the address, what you expected and what you actually see. Ask the owner whether a correction or return to the previous published version is appropriate. Keep the records and current task state while that decision is made.

Before closing the request, retain the approved brief and readable inputs; questions and saved answers; accepted plan or handoff; tested preview URL, revision and QA result; correction/review decisions; merge or operator handoff; publication result; live address; and final checks. That record explains what happened without treating a comment or task status as a release receipt.

For email work, stop at reviewing the draft and its actual storage location until a separate send/schedule process is ready. A task comment, saved Campaigns asset, scheduled message and sent email are different outcomes. See Marketing. For widget-specific steps, see Request Website Changes; for waiting or failed work, see Troubleshooting.

Last updated: 2026-10-25

Operations

Use the agents workspace to request operational work and inspect its status. The tools, integrations, and schedules available to an agent vary by workspace. A task comment describes work; check the connected service or output artifact to confirm the result.

Back to main guide

Admin Docs And Internal References

These public guides come from docs/user-guide/ and are rebuilt with the Glance web app. The developer reference in docs/technical/ is gated on the app host and is not part of the public docs site. Send a broken-guide report with the page title and the step that differs from your screen.

Email Triage (Coordinator Agent)

If an inbox is connected and a triage workflow is enabled, ask the coordinator for the monitored inbox, cadence, routing rules, and last successful run. Open the original message and resulting task or CRM record before relying on a classification. For a new route or reply, request a draft and confirm the recipient and approval path.

Memory System

An agent may use workspace files or a connected knowledge service for context. Ask for the source of a factual answer. Correct a wrong source in the place your workspace uses to store it; a correction in one chat may not update the shared knowledge base.

Outbound Gate (ClawWrap)

Some channels use an outbound target and policy gate. A passed target check does not itself send a message or replace the relevant human approval. To investigate a refused send, give your operator the task link, audience, channel, and safe refusal message. Do not paste credentials into the task.

Glance Agents Lifecycle Bridge

A board task can be assigned to an agent, delegated to a child task, blocked, or placed in review. Open the latest comment and any Waiting on you card. Looks good records a review decision; it does not prove an external action or website publication. See Work With Your Glance Agents.

Heartbeat System

Agents may check for work on a configured schedule or on assignment. No fixed response time applies to every workspace. If a task is idle, check the assignee, paused state, blocked reason, and last comment before filing a duplicate.

Knowledge Sync (Meridian)

A connected sync job may import documents from an approved source. Ask the operator which sources and collections are enabled and when they last synced. A document missing from an answer may mean it was never synced or is outside the agent's access.

Observability (Opik)

Operators may have trace and run records for debugging. Users should share a task link and approximate time when reporting a failure; the operator can look up the relevant run without exposing internal trace data.

Infrastructure (Railway + Mac Mini)

The Glance team manages runtime hosts and integrations. A host or channel listed in older examples is not a promise that your workspace uses it. For a service incident, reply to your latest Glance support email with the workspace, task link, and visible error.

Transcript Ingestion (Curator)

Ask your operator which upload path is configured before sharing a transcript. Review the source permissions and any generated summary. Do not assume an upload automatically updates the agent's knowledge.

Organizational Config

Your workspace has its own configuration and access controls. Request a change through a task or your operator; do not edit a shared repository config file or send a secret in a task.

What Needs Your Approval

Review external messages, publication, financial or participant decisions, and knowledge deletion through the approval process configured for your workspace. A completed board task is not evidence that those separate actions happened.

What Happens Automatically

Only enabled workflows run automatically. Ask for the trigger and last successful run for any automation you depend on.

Back to main guide

Last updated: 2026-10-25

Troubleshooting

The connector says it is not connected

Open Claude Settings → Connectors and check the Glance URL and connection status. Reconnect with the same account used for your workspace. If a different workspace appears during authorization, stop and confirm the correct account and URL with your operator. Refresh Claude's connector settings first. If the connector is still missing in Claude Desktop, restart the app and check again.

The interview feels too short

Ask Claude to go deeper on one answer, offer options, or show what it has saved. Give a concrete example or source URL. If an expected document or preview is missing, ask for its link; contact the Glance team if no artifact was created.

Claude drifted off-topic

Say back to the interview and ask for the current question. Review the summary before accepting the final output.

The preview or docs look wrong

Do not accept an incorrect preview. State the exact text or page to fix. For a website widget request, reply in its Thread. For an agent task, choose Needs changes on the review card or comment on the task. A review decision and live publication are separate; open the live page to verify it.

A task is waiting or blocked

Open its latest comment and check the assignee, any paused agent, the child task, and the Waiting on you card. Reply on the task that asks for your decision. Include the task number when contacting support.

An email draft appeared but nothing was sent

A task comment can hold a draft without a saved campaign asset. Ask for the saved email's version and Details view, then confirm its review, schedule, and send record in the sending service. See Marketing.

Something else is stuck

Reply to your latest Glance support email with the page or task link, the step you took, the visible status, and what you expected. Do not include passwords or API keys.

Copyable support note:

I was on [page or task link]. I clicked [action] at [approximate time].
The screen says [exact status]. I expected [result]. The preview or
publication receipt is [link, if one exists]. Please check the next step.

Appendix A · Connect Claude

Last updated: 2026-10-25

Connect Claude

Glance talks to Claude through a connector — a link between your Claude account and your Glance tenant. Once it's added, Claude can run the Brand Interview and use your Glance tools directly in a chat.

You only need to do this once per Claude account.

Step 1 — Open Connectors in Claude

1. Go to claude.ai and sign in.
2. Open your account menu and choose Settings. The menu's position can vary between Claude web and Desktop.
3. Look for Connectors in your current account settings. It may be under Customize or another settings group; follow the labels shown in your account rather than looking for one fixed sidebar path.

You'll see a list of your connectors — things like Google Drive or Gmail may already be there if you use them. Glance isn't listed yet.

Step 2 — Add the Glance connector

1. Click the Add button in the top-right of the Connectors page.

2. From the dropdown, click Add custom connector.

3. A dialog titled Add custom connector opens with two fields:

   • Name — enter Glance (or a name your team will recognize).

   • Remote MCP server URL — enter your Glance connector URL:

     https://connector.getglance.com/mcp
     

   Leave Advanced settings (OAuth Client ID / Secret) blank — Glance doesn't need them.

4. Click Add.

5. Click Connect on the new connector's row.

Step 3 — Authorize the connection

Clicking Connect opens a new browser tab for authorization.

1. If your workspace sign-in is still active, authorization may continue without another sign-in. Otherwise sign in with your invited account.
2. Review the permissions Claude is requesting, then approve.
3. Claude redirects you back to the Connectors page. Your new connector now shows a checkmark under Status — that means it's connected.

Using Claude Desktop instead of claude.ai? First open a new chat and check whether the connector is available. If it does not appear, refresh the connector settings or restart Claude Desktop, then check again.

If the authorization screen shows a tenant you don't recognize, stop and do not approve — you may have the wrong connector URL. Confirm the URL with your Glance operator before retrying.

Step 4 — Confirm it's working

1. Click your new connector in the list to open its detail panel.
2. You should see:
   • The connector URL (https://connector.getglance.com/mcp) under the name.
   • A Disconnect button (this only appears once you're connected).
   • A Tool permissions section listing the Glance tools Claude can now use (brand interview, brand candidate generation, and related tools).
3. Review each tool permission and choose the approval setting that fits your team's policy. You can approve calls individually.

What Good Looks Like

• The connector shows a checkmark in the Connectors list.
• The connector's detail panel shows Disconnect (not Connect) and lists Glance's tools under Tool permissions.
• You can now start a new chat in Claude and begin the Brand Interview.

Troubleshooting

• "A server with this URL already exists" — you (or someone on your team) already added this connector. Check the existing entry in the Connectors list instead of adding a second one.
• Connector shows no checkmark after authorizing — refresh the Connectors page. If it's still not connected, click the connector, click Connect, and repeat Step 3.
• Wrong tenant during authorization — you're using the wrong connector URL, or you're signed into the wrong email. Confirm both with your Glance operator before retrying.

Appendix B · Migrating from ChatGPT

Last updated: 2026-10-25

Migrating From ChatGPT

If you are used to ChatGPT, Claude will feel similar in some ways and different in important ways.

What Changes

• You can use Claude as a collaborator through several turns.
• The Brand Interview may take multiple turns.
• Claude can offer options, recommendations, and follow-up questions.
• You can correct or redirect the conversation without starting over.

How To Use Claude Well

• Ask for options when you are unsure.
• Ask Claude what it recommends and why.
• Give concrete examples, URLs, names, and stories instead of abstract labels.
• Let Claude ask follow-up questions before forcing a final answer.
• Say back to the interview if the conversation wanders.

Memory And Context

If you have useful ChatGPT memory, notes, or previous drafts, bring the useful pieces over manually and use them as source material in Claude.

If Claude offers a memory import in your account, review the current import screen and select only the context you want to bring across. You can also paste a short summary into the first interview message.

Practical Advice

Start with one clear sentence about the company, then answer the interview one question at a time. If Claude offers A/B/C choices, choose the closest option or explain why none fit.