# Agent access and approvals
Source: https://docs.vecbase.com/administration/access-approvals

Control what each Agent may use and review sensitive actions before they continue.

Each [Agent](/agents/overview) has its own access. Give it only the resources
needed for its current responsibility, then review sensitive actions before
they continue.

## Start with the responsibility

Before adding access, describe the Agent's responsibility in one sentence.
Then ask what it genuinely needs to complete that work.

Access should answer a clear reason, such as:

* read reference files to prepare a summary;
* update one report in a specific file space;
* use one approved Connection to find information;
* run one tool required for the result.

Avoid adding access “just in case.” It is easier to understand an Agent when
each permission has a visible purpose.

## Choose the right access

Open the Agent's access settings and review:

* built-in capabilities it may use;
* [file spaces](/agents/files) it may read, update, or delete;
* [Connections](/workspace/connectors) it may use;
* data or other resources available to it.

Start with read access or a test resource. Add create, change, or delete access
only when the responsibility requires it.

## Use approvals

Some actions need a person to review and approve them. A useful approval should
show:

* what the Agent is about to do;
* which resource will change;
* why the action is needed;
* whether it can be reversed.

Do not approve an action you do not understand. Ask the Agent to explain it in
plain language first. A [Scheduled Task](/agents/scheduling) cannot bypass the
same approval.

## Review regularly

Review an Agent's access when:

* its responsibility changes;
* a project ends;
* a connected account changes;
* a Scheduled Task is no longer needed;
* files or data move to a different place.

Remove access that no longer has a clear purpose.

<Tip>
  **Small access is easier to trust**

  Begin with the smallest useful scope. Increase it only after the Agent has
  shown why the additional access is needed.
</Tip>


# Security and your data
Source: https://docs.vecbase.com/administration/security-data-retention

Keep access narrow, protect secrets, and understand how files and resources are kept or removed.

Good security in Vecbase starts with clear access and simple habits. Give each
Agent only what it needs, then
[review that access](/administration/access-approvals) as work changes.

## Control access

Keep sensitive work in the correct workspace and file space. Give each Agent
specific access to the resources its responsibility requires.

Before adding access, ask:

1. Does this Agent need the resource for its current responsibility?
2. Is read access enough?
3. Does a person need to approve changes or deletion?
4. When should this access be removed?

## Protect secrets

Use Vecbase's [Connection](/workspace/connectors) and credential screens for
private account details. Do not place passwords, secret keys, access tokens, or
one-time codes in:

* Agent instructions;
* task messages;
* files intended for broad sharing;
* screenshots;
* support requests.

If a secret was exposed, revoke or replace it at the source, then update the
Connection.

## Understand where data stays

Different places have different lifetimes:

* the [**File Library**](/agents/files) keeps shared files until you or an
  Agent with delete access removes them;
* a [**Dedicated cloud computer**](/agents/work-environments) keeps that Agent's
  working files while the resource exists;
* a **Temporary workspace** starts fresh for a new conversation;
* task messages and delivered results remain part of the workspace history
  according to the product's current controls.

Move important shared work to the File Library. Do not rely on a temporary
working area as the only copy.

## Suspension and removal

When [billing](/workspace/billing) is suspended, work pauses first. Vecbase
does not immediately remove workspace resources. A recovery period of at least
seven days begins, with notifications to the team before automatic cleanup can
complete if billing is not restored.

Manual deletion is different. Deleting a file, file space, Agent, or workspace
can be permanent. Read the confirmation carefully and move anything the team
needs before approving it.

## A simple safety checklist

* review Agent access after a role or project changes;
* keep delete access uncommon;
* pause unused [Scheduled Tasks](/agents/scheduling) and cloud computers;
* store shared results in the right file space;
* never share secrets in chat or support;
* ask for approval before sensitive or hard-to-reverse work.

If you believe access or data has been exposed, stop the affected task or
Connection and [contact support](/workspace/support) promptly.


# What Agents can do
Source: https://docs.vecbase.com/agents/capabilities

Understand the built-in tools and services an Agent can use for files, research, media, data, and everyday work.

[Agents](/agents/overview) can use Vecbase tools and services to do more than
write a reply. The exact choices shown to you depend on the workspace, plan,
and Agent setup.

## Built-in help

When you create or edit an Agent, Vecbase shows the tools and AI services
currently available. Start with the recommended choices. You can return to the
Agent's settings when a real task needs something more.

## Common types of work

Depending on what is available, an Agent may be able to:

* read, create, and organize files;
* search the web and collect public information;
* work with documents and structured information;
* create or understand images, audio, or speech;
* use approved data sources;
* complete work inside its chosen
  [work environment](/agents/work-environments).

Availability can change, so the Agent creation and settings screens are the
source of truth for your workspace.

## Choose during setup

Give an Agent the smallest useful set of capabilities. A writing Agent may need
documents and images, while a research Agent may need web search and selected
data sources.

Too many choices can make an Agent harder to understand. Add a capability when
you can name the task that requires it.

## Understand access

These three ideas are different:

| Item                                | What it means                                     |
| ----------------------------------- | ------------------------------------------------- |
| Capability                          | A tool or service Vecbase provides                |
| [Connection](/workspace/connectors) | An external app or account your team approves     |
| [Skill](/agents/skills)             | A reusable method installed for an eligible Agent |

Seeing a capability in Vecbase does not always mean every Agent may use it. The
workspace plan, Agent settings, available credits, and resource access all
matter.

If an Agent cannot use something, first open its settings and confirm that the
option appears and is enabled. Then check
[access](/administration/access-approvals) and
[billing](/workspace/billing) before changing the task.


# File Library
Source: https://docs.vecbase.com/agents/files

Organize shared team files in file spaces and decide which files each Agent may use.

The **File Library** is the shared home for files your team wants to keep. It
is separate from the
[Temporary workspace](/agents/work-environments) used to complete a task.

## What the File Library is

Use the File Library for source documents, shared references, and finished
work that people or [Agents](/agents/overview) will need again.

You can upload, preview, download, rename, move, and delete files. Folders help
you keep related work together.

## Organize with file spaces

A **file space** is a top-level area inside the File Library. Create one for a
project, topic, or access boundary—for example, “Brand,” “Customer Research,”
or “Finance Reports.”

Choose names that make sense to the whole team. Use folders inside a file
space for smaller sections.

<Steps>
  <Step title="Open File Library">
    Open the workspace and choose **File Library**.
  </Step>

  <Step title="Create a file space">
    Choose **New file space**, enter a clear name, and make it the default only
    if most new files should go there.
  </Step>

  <Step title="Add files or folders">
    Upload existing files or create folders before adding more material.
  </Step>
</Steps>

## Work with files

Select a file to preview it when the format is supported. Download it when you
need the original or when browser preview is not available.

Renaming and moving help keep things tidy. Deleting a file or file space is
permanent, so check the selection before confirming.

## Give an Agent access

An Agent does not need every file. Open its
[access settings](/administration/access-approvals), choose the file space
it needs, and allow only the actions required for the job:

* read files;
* create or update files;
* delete files.

For many roles, read and write access is enough. Add delete access only when
removing files is part of the Agent's responsibility.

## Know where files live

| File location            | Use it for                                            |
| ------------------------ | ----------------------------------------------------- |
| File Library             | Shared files and results the team needs again         |
| Task attachment          | Material for one conversation                         |
| Dedicated cloud computer | One Agent's ongoing working files and installed tools |
| Temporary workspace      | Short-lived work during one conversation              |

<Tip>
  **Save the result where it will be used**

  If another person or Agent will need the result later, place it in the right
  file space instead of leaving it only inside a conversation.
</Tip>


# Agents
Source: https://docs.vecbase.com/agents/overview

Learn how to create an AI teammate with a clear role, give it useful tasks, and improve it over time.

An Agent is an AI teammate set up for a particular responsibility. You talk to
it in ordinary language, review its work, and decide what it may use.

## What an Agent is

Each Agent has its own:

* name and role;
* instructions;
* AI model;
* work environment;
* tools, files, and connections it can access;
* task history.

Keeping these separate makes it possible to have several focused Agents
without giving every one of them the same information or access.

## Create a useful Agent

Start with a responsibility you can describe in one sentence. Then write a
short instruction that covers:

1. what result the Agent should produce;
2. what information it should use;
3. what “good” looks like;
4. what it must ask before doing.

For example: “Prepare a clear weekly project update from the latest notes.
Highlight decisions, delays, owners, and questions. Ask before changing any
source file.”

## Give better tasks

For each task, tell the Agent:

* the outcome you want;
* the useful background;
* any deadline or limits;
* the format you prefer;
* where to save the result.

If the first answer is not right, explain what is missing. The same task keeps
the conversation and attached context together.

## Improve over time

Review the Agent's results before increasing its responsibility. When you see
a repeated correction, add it to the Agent's instructions or turn the method
into a [Skill](/agents/skills).

Use a new task for a new goal. Keep long-running project files on a Dedicated
cloud computer or in the File Library, depending on who needs them.

## Add more when needed

<CardGroup>
  <Card title="Work environments" href="/agents/work-environments">
    Choose between a fresh temporary workspace and a dedicated cloud computer.
  </Card>

  <Card title="File Library" href="/agents/files">
    Organize shared files and give an Agent the right access.
  </Card>

  <Card title="Skills" href="/agents/skills">
    Reuse a proven way of working.
  </Card>

  <Card title="Scheduled Tasks" href="/agents/scheduling">
    Run repeat work at a time you choose.
  </Card>
</CardGroup>


# Scheduled Tasks
Source: https://docs.vecbase.com/agents/scheduling

Ask an Agent to run one-time or recurring work at a time you choose.

Scheduled Tasks let an [Agent](/agents/overview) do work later or repeat it on
a regular rhythm. They are useful for daily summaries, weekly reports, routine
checks, and other work with a clear schedule.

## What Scheduled Tasks do

Each Scheduled Task belongs to one Agent. When the chosen time arrives, that
Agent receives the saved instruction and runs a new task.

You can choose a one-time date or a repeating interval, daily, weekly, or
monthly schedule. Vecbase shows the schedule in the timezone you select.

## Create a Scheduled Task

<Steps>
  <Step title="Choose the Agent">
    Open the Agent that has the right role and access for this work.
  </Step>

  <Step title="Add the instruction">
    Give the task a clear name and describe the exact result to produce.
  </Step>

  <Step title="Choose when it runs">
    Select the frequency, date or days, time, and timezone.
  </Step>

  <Step title="Review and enable">
    Check the summary, confirm where the result should go, and enable the task.
  </Step>
</Steps>

## Write clear instructions

Write the instruction so it is safe to run again. In everyday language, tell
the Agent:

* which dates or records to include;
* where to save the result;
* how to avoid creating the same result twice;
* how much information to check at one time;
* what to do when an expected input is missing;
* how to report “nothing new” differently from “the task failed.”

For example: “Every Monday, summarize updates from the previous seven days.
Update the existing weekly report in the Project Updates file space. If there
are no new updates, say so. If a source cannot be opened, list the source and
stop without replacing last week's report.” Learn how to choose and share a
[file space](/agents/files).

## Review results

Open **Scheduled Tasks** on the Agent to see whether a task is active and to
review its run history. Check the first few results closely.

If a task fails repeatedly, it may pause. Check that the Agent can still open
the needed files or [Connections](/workspace/connectors), that
[billing](/workspace/billing) is active, and that the instruction still
matches the source.

## Approvals still apply

<Warning>
  **Automation does not remove approval**

  A Scheduled Task cannot bypass an approval that the same action would need
  during a normal conversation. Avoid scheduling destructive or sensitive
  work unless the [review path](/administration/access-approvals) is clear.
</Warning>

Pause or delete a Scheduled Task when the result is no longer needed. Changing
it affects future runs, not work already completed.


# Skills
Source: https://docs.vecbase.com/agents/skills

Help an Agent repeat a proven way of working by adding a reusable Skill.

A Skill gives an [Agent](/agents/overview) a reusable method for a familiar
kind of work. Think of it as a small playbook the Agent can follow again.

## What a Skill is

A Skill can contain instructions and supporting files. It can describe how to
prepare a report, review a document, organize research, or complete another
repeatable process.

Skills do not give an Agent extra authority by themselves. The Agent still
needs access to any files, tools, or
[Connections](/workspace/connectors) used by the work.

## When to use one

Create or install a Skill when:

* you keep giving the same explanation;
* the order of steps matters;
* a shared template or reference should always be used;
* you want a more consistent result.

For a one-time request, a clear task instruction is usually simpler.

## Add a Skill

Open an eligible Agent and choose **Skills**. You can upload a Skill or install
one from a source offered by Vecbase. Review its name, description, and files
before using it.

Then start a task and choose the Skill when it fits the work. You can still add
task-specific details in your message.

<Warning>
  **Review before installing**

  A Skill can guide an Agent to use its available tools. Only add Skills from a
  source you trust, and remove ones the Agent no longer needs.
</Warning>

## Keep Skills useful

Treat a Skill like a short team playbook:

* explain the desired result first;
* use simple steps;
* state what to do when information is missing;
* avoid old names, paths, or assumptions;
* test it on a small task after a change.

If a Skill produces confusing results, simplify its instructions before adding
more rules.

## Availability

The current Skill manager is available for Agents using a
[**Dedicated cloud computer**](/agents/work-environments). Skills are installed
for that Agent and are not automatically shared with every Agent in the
workspace.

Agents using a **Temporary workspace** do not show the same Skill management
area. Choose the work environment based on the job, not only to gain more
features.


# Choose a work environment
Source: https://docs.vecbase.com/agents/work-environments

Choose a Temporary workspace for one-off work or a Dedicated cloud computer for ongoing projects.

The work environment is the place where an [Agent](/agents/overview) handles
files and completes its task. Vecbase offers two simple choices.

## Two choices

| Choose                   | Best for                                                     | What stays                                                                      |
| ------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| Temporary workspace      | One-off tasks and a simple first Agent                       | The conversation and delivered results; the working area starts fresh next time |
| Dedicated cloud computer | Ongoing projects that need the same files or installed tools | Files, tools, and work progress on that Agent's computer                        |

## Temporary workspace

A Temporary workspace gives each new conversation a clean working area. It is
the recommended choice when you want to summarize a file, prepare a draft, do
research, or complete another self-contained task.

Because it starts fresh, do not treat its working area as long-term storage.
Save important results to the [File Library](/agents/files) or download them.

## Dedicated cloud computer

A Dedicated cloud computer belongs to one Agent. Choose it when that Agent
needs to continue a project over time, keep installed tools, or return to the
same working files.

It may take a short time to start. You can stop it when it is not needed and
start it again later.

## Which one to choose

Choose a **Temporary workspace** unless you can clearly finish this sentence:

> This Agent needs the same working files or installed tools next time because…

If several people or Agents need the files, use the **File Library** instead of
relying only on one Agent's cloud computer.

## Files and cost

A Dedicated cloud computer can have an ongoing storage cost, and running it can
use additional [credits](/workspace/billing). The current choices and prices
appear in Vecbase when you create or edit an Agent.

Changing an Agent's work environment can affect which local files and
[Skills](/agents/skills) are available. Move important shared results to the
File Library before making a change.


# The basics
Source: https://docs.vecbase.com/getting-started/concepts

Understand the few simple ideas behind workspaces, Agents, tasks, files, and access in Vecbase.

You only need a few ideas to get comfortable with Vecbase.

## Workspaces

A [**workspace**](/workspace/overview) is where a team keeps a related area of
work. It contains the Agents, tasks, files, connections, and settings for that
work. A team can use one workspace or separate workspaces for different
projects or access needs.

## Agents and tasks

An [**Agent**](/agents/overview) is an AI teammate you set up for a
responsibility. It has a name, instructions, a chosen model, a work
environment, and access you control.

A **task** is one piece of work or one conversation with that Agent. New tasks
are useful when the goal or context changes.

<Tip>
  **Name the responsibility**

  “Customer Research” is easier to manage than “My AI.” A clear name reminds
  everyone what the Agent should and should not do.
</Tip>

## Files

The [**File Library**](/agents/files) is the shared home for team files. Inside
it, **file spaces** keep files organized by project or purpose.

Files attached to a task are available for that piece of work. Files on a
Dedicated cloud computer stay with that Agent. These are different from the
team's File Library, so save important shared results in the right file space.

## Skills and connections

A [**Skill**](/agents/skills) is a reusable set of instructions for a familiar
kind of work. It helps an Agent follow the same method again.

A [**Connection**](/workspace/connectors) links an approved external app or
account to the workspace. Connecting an account does not automatically give
every Agent access. You choose which Agent may use it.

Built-in capabilities, Skills, and Connections solve different needs. Start
with what Vecbase already provides, then add only what the work requires.

## Access and approvals

Access answers a simple question: **who or what may use this resource?**

[Agent access and approvals](/administration/access-approvals) decide which
tools, file spaces, and connections an Agent may use. Sensitive actions may
ask a person to approve them before they continue.

[Billing](/workspace/billing) also affects availability. When a needed plan or
credit balance is not available, new work pauses instead of running without
control.


# Welcome to Vecbase
Source: https://docs.vecbase.com/introduction

A simple introduction to building an AI team in Vecbase, written for people with no technical background.

Vecbase gives your team one place to work with AI. You can create AI teammates,
give them work, share the right files and tools, and review what they do.

You do not need to know how AI models or software systems work. Start with one
useful task and grow from there.

## What Vecbase does

Vecbase brings the pieces of AI work together:

* **Agents** are AI teammates with a name, a role, and their own settings.
* **Tasks** are the pieces of work you give an Agent.
* **File Library** keeps shared team files organized in file spaces.
* **Connections** let an Agent use an account or app that you approve.
* **Skills** help an Agent repeat a familiar way of working.
* **Scheduled Tasks** run useful work at a time you choose.

You can begin with only an Agent and a Task. Everything else is optional.

## Your AI team

Create an Agent for a clear responsibility, such as preparing a weekly report,
organizing research, drafting content, or checking a list of updates. Then talk
to that Agent in everyday language.

Good instructions explain the result you want, the background that matters,
and where the finished work should go. You can refine the request while you
work, just as you would with a new teammate.

## You stay in control

An Agent can only use the tools, files, and connected accounts available to it.
You decide which of these resources each Agent may use.

Important or sensitive actions can still require approval. A scheduled task
does not remove those checks.

<Tip>
  **Start small**

  Give one Agent one clear responsibility. Review a few results, improve its
  instructions, and only then add more access or automation.
</Tip>

## Start here

<CardGroup>
  <Card title="Create your first Agent" href="/quickstart">
    Follow a short guide from sign-in to your first finished task.
  </Card>

  <Card title="Learn the basic ideas" href="/getting-started/concepts">
    Understand workspaces, Agents, tasks, files, and permissions.
  </Card>

  <Card title="Set up the File Library" href="/agents/files">
    Keep shared files in simple, organized file spaces.
  </Card>

  <Card title="Automate repeat work" href="/agents/scheduling">
    Ask an Agent to run useful work at the right time.
  </Card>
</CardGroup>


# Create your first AI teammate
Source: https://docs.vecbase.com/quickstart

Create an Agent, give it a clear first task, and review the result in a few simple steps.

This guide takes you from signing in to finishing your first task. No coding or
AI experience is needed.

## Before you start

Think of one small result you would genuinely use. For example:

* summarize a document;
* turn meeting notes into an action list;
* compare a few options;
* draft a short announcement.

A clear, real task makes it easier to learn what your Agent does well.

## Open your workspace

<Steps>
  <Step title="Sign in to Vecbase">
    Open Vecbase and sign in. Choose the workspace where this work belongs.
  </Step>

  <Step title="Check the workspace name">
    A workspace keeps one team's Agents, files, connections, and settings
    together. You can rename it later.
  </Step>
</Steps>

## Create an Agent

<Steps>
  <Step title="Choose New Agent">
    Give the Agent a simple name that describes its responsibility, such as
    “Research Assistant” or “Weekly Report.”
  </Step>

  <Step title="Choose a work environment">
    Use the recommended **Temporary workspace** for a first, one-off task.
    Choose a **Dedicated cloud computer** only when work must continue over
    time.
  </Step>

  <Step title="Keep the first setup simple">
    The recommended model and settings are enough to begin. Add special tools,
    files, or connections only when the task needs them.
  </Step>
</Steps>

## Give your first task

Open the Agent, choose **New Task**, and describe the result in everyday
language.

A useful first instruction might be:

> Read the attached meeting notes. Give me the five most important decisions,
> the owner of each follow-up, and anything that still needs a decision.

Attach the relevant file, send the task, and review the response. If something
is missing, say what to change. You do not need to start over.

## Keep the result

Download a finished file when you need a local copy. For work the team will use
again, save it in the **File Library**. File spaces help keep projects or topics
separate.

<Warning>
  **Temporary work is not long-term storage**

  A Temporary workspace starts fresh for each conversation. Save anything
  important to the File Library or download it before you rely on it later.
</Warning>

## What next

Once the first result is useful, choose one next step:

* [improve the Agent's role and instructions](/agents/overview);
* [give it access to a file space](/agents/files);
* [connect an approved app or account](/workspace/connectors);
* [turn repeat work into a Scheduled Task](/agents/scheduling).

Add one capability at a time. It keeps the Agent easier to understand and
control.


# Billing, credits, and usage
Source: https://docs.vecbase.com/workspace/billing

Understand where to view plans, credits, usage, and what happens when a balance is not available.

Open **Billing & usage** from the current workspace to see its plan, credits,
usage, available options, and current prices.

## Where billing lives

The billing page shows the plan and credit balance available for work in the
workspace. **Usage** helps you understand where that balance is being used.

Billing controls appear when they are available to the current account.

## Plans and credits

A plan determines which product features and limits are available. Credits pay
for usage such as AI models and running cloud resources.

Different models and types of work can use credits at different rates. Check
the price shown in Vecbase when choosing a model or cloud computer rather than
relying on an old estimate.

## Review usage

Use the **Usage** page to look for:

* which workspace is using credits;
* whether a particular [Agent](/agents/overview) or repeated task is
  unexpectedly active;
* ongoing cloud computer use;
* changes after adding a new model, capability, or
  [Scheduled Task](/agents/scheduling).

Review the pattern, not only one task. A recurring task may use a small amount
each time but become meaningful over a month.

## When work pauses

If the usable balance runs out or billing is suspended, new Agent work and
cloud resources pause. Scheduled Tasks cannot run around that pause.

Add credits or resolve the billing issue from **Billing & usage**. Once access
is restored, check any task that should be started again.

<Warning>
  **Paused work is a safety boundary**

  A spending limit can add another boundary, but it does not replace the need
  for an available credit balance.
</Warning>

## Keep spending clear

* stop Dedicated cloud computers that are not being used;
* pause Scheduled Tasks whose results are no longer read;
* choose a model that fits the importance of the work;
* review usage after giving an Agent a new responsibility;
* only use billing controls from the account responsible for them.

For help with an unexpected charge or balance, open a
[support request](/workspace/support) and include the date, workspace, and
visible usage details. Never send payment secrets.


# Connections
Source: https://docs.vecbase.com/workspace/connectors

Connect an approved app or account to a workspace and choose which Agent may use it.

A Connection lets Vecbase use an external app or account that your team
approves. It can help an [Agent](/agents/overview) work with information
already stored elsewhere.

## What a Connection is

A Connection belongs to a [workspace](/workspace/overview). The
**Connections** screen shows the apps currently available and guides you
through their sign-in or setup.

Connecting an account and giving an Agent access are two separate choices. This
keeps one connected account from automatically becoming available to every
Agent.

## Connect an account

<Steps>
  <Step title="Open Connections">
    Choose **Connections** in the workspace.
  </Step>

  <Step title="Choose an available app">
    Select the app you need and review what Vecbase is asking to access.
  </Step>

  <Step title="Sign in and approve">
    Use the account that owns the needed information. Complete the provider's
    approval screen.
  </Step>

  <Step title="Confirm the connection">
    Return to Vecbase and check that the account appears as connected.
  </Step>
</Steps>

The available apps can change. Use the Connections screen as the current list
for your workspace.

## Give an Agent access

Open the Agent's [access settings](/administration/access-approvals) and
select the specific Connection it needs. If the app offers narrower choices,
select only the area required for that Agent's work.

Test with a small, reversible task first. For example, ask the Agent to find or
summarize information before asking it to create or change anything.

## Manage or remove

Remove Agent access when its role changes. Disconnect the account from the
workspace when the team no longer uses it or when the connected account should
change.

Disconnecting stops future use through Vecbase. It does not normally delete
the original information in the external app.

<Warning>
  **Keep sign-in details private**

  Never paste passwords, secret keys, or access tokens into a task or support
  message. Follow the [security guidance](/administration/security-data-retention)
  and use the Connection setup screen so credentials are handled through the
  intended flow.
</Warning>

## If it stops working

Check these in order:

1. the Connection still shows as active;
2. the Agent still has access to it;
3. the external account still has permission to the requested information;
4. the account owner has not revoked or changed access.

If needed, reconnect the account and retry a small task.


# Workspaces
Source: https://docs.vecbase.com/workspace/overview

Keep a team's Agents, files, connections, and settings together in clear workspaces.

A **workspace** is the home for one team's related work. It keeps AI
teammates, files, connections, and settings for that work together.

## What a workspace contains

Each workspace can contain:

* [Agents](/agents/overview) and their tasks;
* the [File Library](/agents/files);
* [Connections](/workspace/connectors);
* workspace settings, usage, and support requests.

## Decide your structure

Start with one workspace when related work can safely share the same resources.
Create another workspace when you need a clear boundary—for example, a
separate client project, a private area, or different access needs.

Avoid creating a workspace for every small task. Agents, tasks, and file spaces
already help keep work clear inside a workspace.

<Tip>
  **Use names people recognize**

  Name a workspace after the work it contains, such as “Product,” “Operations,”
  or a project name. Add a short description so its purpose is clear.
</Tip>

## Everyday management

From the workspace menu, you can:

* rename the workspace and update its description;
* choose the workspace timezone;
* create and manage Agents;
* open the File Library and Connections;
* review [usage and billing](/workspace/billing);
* [contact support](/workspace/support).

Deleting a workspace is permanent and has safety checks. Remove or move
anything the team needs before starting that process.


# Get help
Source: https://docs.vecbase.com/workspace/support

Try a few quick checks, then send the Vecbase team the information needed to help you.

When something does not work as expected, a few simple checks often solve it.
If they do not, contact the Vecbase team from your workspace.

## Quick checks

Before opening a request:

1. refresh the page once;
2. confirm you are in the intended [workspace](/workspace/overview);
3. check that the Agent or [Scheduled Task](/agents/scheduling) is active;
4. confirm the Agent still has access to the needed
   [file space](/agents/files) or [Connection](/workspace/connectors);
5. review [**Usage** or **Billing**](/workspace/billing) for a paused balance or
   plan limit;
6. try a smaller version of the same task.

Do not repeatedly submit an action that creates, sends, or deletes something.
Check whether the first attempt already finished.

## Open a support request

Open **Support** in the workspace and create a new request. Choose a short
title that describes the visible problem, such as “Weekly task stopped
running” or “File preview stays blank.”

Keep one issue in each request. This makes updates easier to follow.

## What to include

Tell the support team:

* what you were trying to do;
* what you expected to happen;
* what happened instead;
* the approximate time and your timezone;
* the workspace, Agent, or task name;
* the exact error text, if one appeared;
* a screenshot with private information hidden.

Simple steps such as “open Agent, choose Scheduled Tasks, select Weekly Update”
are especially helpful.

## What not to send

<Warning>
  **Never send secrets**

  Do not include passwords, one-time codes, secret keys, access tokens, or full
  private documents. The support team does not need them to investigate.
</Warning>

## Follow the reply

Return to **Support** to read replies and add information. If the issue changes
or a new issue appears, open a separate request instead of mixing unrelated
problems.

When the issue is resolved, keep the final explanation if it will help your
team next time.