Skip to main content
A project is the shared workspace in Parlé. Everything the team does for a piece of work lives inside it: conversations everyone on the project can see and continue, the project’s files, a spending budget, standing instructions for the agent, and the tools it is allowed to use. Creating one takes under a minute. The parts that make it genuinely useful — members, storage, context, budget — are set up afterwards from the project’s own tabs.
You’ll need: to be an Org Admin. Creating projects is Org Admin only; once a project exists, its Project Admins run it day to day.
Worth doing first: connect at least one AI model for your organization — see Connecting Providers. A project without any enabled models can be created, but nobody will be able to chat in it.

​
Creating a project

1

Open the New project form

Go to Projects and select New project (top right).
2

Name and describe it

  • Name — required, e.g. Q3 Research. Shown on the project card and everywhere the project is referenced.
  • Description — optional; one line on what the project is for.
  • Project code — optional; your own accounting reference for the project, such as a matter number, cost centre or expense code. It appears beside the project’s spend in usage reports and CSV exports. See Expense Codes.
3

Choose visibility

  • Public — anyone in your organization can open this project. Members are still used to decide who is a Project Admin.
  • Restricted — only people you add as members can open it. Use this for client-confidential or sensitive work.
4

Set a budget

  • Budget currency — the currency this project’s spending caps are stated in: USD, CAD, EUR or GBP. Pick the one you report this work in — it is fixed once the project records any spend.
  • Cap period — whether the amount below is a limit for Every month (spending resets on the 1st) or a Total, for the life of the project. Monthly is the default.
  • Monthly cap / Total cap — how much the project may spend over that period, in the currency above. Set 0 for no limit — spend is still tracked, and the project is created with no cap at all. (On the Budget tab afterwards, a cap is switched on or off with a tick rather than by typing 0, so a ticked cap there needs an amount above zero.)
The Budget currency you pick here is saved together with the cap. A project created with the amount at 0 has no cap to attach it to, so it starts in USD whatever you picked. To use another currency, open the project’s Budget tab and set it there before the project records any spend — after that it is fixed.
You can change the amount later, and add the other cap, from the project’s Budget tab. See Budgets.
5

Choose available models

Every model your organization has enabled is ticked by default. Untick any you want to block for this project, for example to keep an expensive model off a high-volume project. This section only appears if your organization has models connected. After creation, blocked models and any other rules for this project live in its model policy, on the Budget tab.
6

Choose storage

Parlé Cloud Storage needs no setup and is the default. If your organization has connected SharePoint or Google Drive, you can point the project at it after creation.
7

Create the project

You land in the project’s workspace, already added as its Project Admin.
Visibility cannot be changed from the project’s tabs later — decide it now. If you are unsure, Restricted is the safer choice; you can always add the whole team as members.

​
The project workspace

The project workspace has one tab per area of setup.

Conversations

Shared AI threads. Everyone on the project sees them and can pick any of them up.

Files

The project’s file area, which the team and the agent both use.

Project Details

Storage configuration and agent.md, the project’s standing instructions.

Members

Who is on the project, and who administers it.

Budget

The project’s monthly and lifetime caps and actual spend per conversation, plus its model policy, per-message spending limit and Auto starting tier.

Tools

Which of your organization’s connected integrations this project may use.

​
Adding members

On a Restricted project the member list is the access list. On a Public project everyone in the organization can already open it, so this mainly decides who the admins are.
1

Open the Members tab

Under Add an org member, pick the person.
2

Set their access

Project Admin — can edit project details, the context file, storage, and membership. Project Member — can use the project.
3

Optionally set a project role

Free text describing what they do here, e.g. Business Analyst. It is a label for the team, not a permission.
4

Select Add member

Repeat for everyone who needs access.
Change someone’s access or role directly in the roster, or Remove them. Every project must keep at least one Project Admin — removing the last one is refused.
People must already be members of your organization before they can be added to a project. See Managing Members.

​
Pointing the project at storage

Every project has a file area the team and the agent both use. By default that is Parlé-managed storage, which works immediately. If your organization has connected SharePoint or Google Drive, you can instead root the project in a document library or Shared Drive so files stay in your own tenant.
1

Open Project Details → Storage

Choose a provider.
2

Parlé Cloud Storage

Managed storage, no setup.
3

SharePoint

Paste the site URL (e.g. https://contoso.sharepoint.com/sites/Marketing) and select Resolve, choose a document library, and optionally a folder within it to root the project at.
4

Google Drive

Paste the URL of the Shared Drive itself — its root, not a sub-folder inside it.
5

Save storage

Parlé checks it can actually reach the location before saving, so a permissions gap is caught now.
SharePoint and Google Drive only appear if an Org Admin has enabled them for your organization, and each needs its own tenant-side permission grant first — see Connect Microsoft 365 and Connect Google Workspace.

​
Project context (agent.md)

agent.md holds standing instructions for the agent — the equivalent of a project brief, injected at the start of every conversation in the project. This is the single highest-leverage thing you can set up on a new project. See Shared Context.

​
Enabling tools

If your organization has connected integrations, open the Tools tab and switch on the ones this project should have. Nothing is enabled by default — an integration is available to a project only once it is toggled on there. See Integrations.

​
Archiving and restoring a project

When a project is finished, an Org Admin can archive it instead of leaving it in the active list. Archiving is Org Admin only — a Project Admin can see the control but cannot use it.
Archiving permanently deletes the project’s knowledge sources and integration connections. Restoring the project later brings the project itself back, but not that deleted data. Conversations and files are not affected either way — archiving and restoring never touch them.
1

Open Project Details → Danger Zone

Scroll to the bottom of the project’s Details tab.
2

Select Archive

Type the project’s name exactly to confirm, then select Archive project. This extra step exists because the data loss above is real and cannot be undone by restoring.
An archived project:
  • Stops counting against your subscription’s project limit.
  • Drops off everyone’s Pinned list (their pin is kept and reappears automatically if the project is restored).
  • Stays fully readable — anyone who could open it before can still open it, browse its conversations, and read its files.
  • Loses team access to any Microsoft 365 or Google Workspace integrations it had connected, and every knowledge source it owned — both are deleted, not paused.
To restore one, go to the Projects page and open the collapsed Archived section at the bottom of the list. Each archived project’s card has a Restore button — a single confirm click, since restoring destroys nothing.

​
Troubleshooting

Still stuck? Contact Parlé support with your organization name and the project name.