Files

Files is your organization’s shared workspace — the documents Adlyse works from, as opposed to the numbers it reports on. Briefs, playbooks, house rules, saved research, anything you’d otherwise have to re-explain in every conversation. Agents with folder access read and write here too, so it’s the common ground between you and them.

In one line

Anything you find yourself pasting into a chat more than twice belongs in Files.

Getting things in#

Open Files from the sidebar. You can create folders, create markdown files directly, upload from your machine (drag a folder in and its structure comes with it), and move things around by dragging. Files are versioned, so an edit is never destructive — you can look at earlier versions and promote one back.

Guidelines: standing instructions#

The guidelines/ folder is special. A markdown file in there becomes a standing instruction that Adlyse follows on every message — your do’s and don’ts, escalation rules, and platform playbooks. There’s no separate step to switch one on; create the file and it’s picked up on the next message.

Every organization starts with one: guidelines/adlyse.md, covering how much the assistant may do on its own, what it must confirm first, and what it must never touch. It’s a starting point, not a fixed policy — edit it to match how your team actually operates.

The filename decides when a guideline applies. Name one after an ad platform and it only applies when that platform is connected:

File	Applies
`guidelines/adlyse.md`	Always
`guidelines/google.md`	Only when a Google Ads account is connected
`guidelines/meta.md`	Only when a Meta account is connected
`guidelines/microsoft.md`	Only when a Microsoft Ads account is connected
`guidelines/chatgpt.md`	Only when a ChatGPT Ads account is connected
`guidelines/anything-else.md`	Always

So a Google rule never bleeds into a Meta conversation, and a playbook for a platform you haven’t connected yet costs nothing to write early. Any other name — creative-review.md, client-reporting.md — is a house rule that always applies.

Platform playbooks aren't pre-written

Only adlyse.md ships with starter content. Bid strategies, naming conventions, and creative standards differ far too much between accounts for a default to be right, and a rule nobody read is worse than no rule. Write the ones you want.

There is no brand guideline file

Brand context used to live in a guidelines/brand.md file. It doesn’t any more — it comes from your Brand profile, which is rendered live into every conversation. Maintain your positioning there, in one place, rather than in a document that can drift out of date. Any leftover brand.md from before the change is archived and ignored.

Writing a good guideline#

Write them the way you’d brief a new teammate — short, direct, specific. The ones that earn their keep tend to be the ones that encode a decision you’d otherwise have to make again:

plaintext

Never propose changes to brand-term campaigns without flagging it explicitly.
Report in plain language — assume the reader is a founder, not a media buyer.
Escalate anything over $2,000/mo of impact to a human before proposing it.

Changes take effect on the next message.

Files and agents#

An agent with the Folder access capability can browse and edit this workspace — read your briefs before writing a report, and file its own output where your team will find it. It’s one of the more useful capabilities to turn on, and one of the few where “can write” is genuinely what you want.

See tool groups for the details.

Common flows#

Stop repeating yourself. Write the context you keep pasting into chats as a house-rule guideline once.
Codify a platform playbook. Put your Meta rules in guidelines/meta.md and they’ll stay out of Google conversations.
Give agents somewhere to file things. Point a scheduled reporting agent at a folder and let it deposit each run’s output.

Brand profile

Positioning, audience, and objectives — the context, not the rules.

Tables

Structured rows, for when a document isn’t the right shape.

Skills

A guideline applies always; a skill applies to one kind of task.

Tool groups

Give an agent folder access — and understand what that grants.

For developers

Read and write the same workspace with list_files, read_file, write_file, and grep_files; guidelines are also readable via list_guidelines and get_guideline.