Project instructions

What project instructions do

Project instructions hold preferences that should apply across conversations in the same project: terminology, response style, design conventions, or constraints that repeatedly matter. They are not a replacement for the current task, application configuration, or secure credentials.

Add or change instructions

1. Open the project workspace.
2. Select Settings, the last tab in the right-hand panel.
3. Enter your text in Project instructions.
4. Select Save in the header.

Only saved text takes effect. Closing the panel is not a substitute for saving. To remove custom guidance, clear the field and save the empty value.

For example:

Keep explanations concise. Use “member” rather than “customer” in this project. Reuse existing interface components and keep every main page accessible by its own URL.

Who can save changes?

The project owner and invited users with full access can edit instructions when the project owner's plan includes the capability. View-only access does not allow editing. Availability depends on the enabled plan functions; do not assume every paid plan includes it. See Plans and credits.

If the owner’s plan does not include the capability, that restriction is shown first. Saved instructions remain stored but are not applied while the capability is unavailable. You can still give the agent ordinary requests in chat. Otherwise, users without editing permission see a separate access message.

If another collaborator saves first, your outdated version is rejected rather than silently overwriting their changes. Review the latest saved text, reconcile your edits, and save again.

When do changes apply?

Saved instructions apply to new tasks. A task that has already started keeps the instructions it received at its start. Saving new guidance does not inject it into work already running.

Amazi keeps the saved text as entered until an authorized user changes it; it does not rewrite it into a generated summary. This does not mean the assistant will obey every instruction regardless of the current request: platform rules, permissions, and safety boundaries still apply.

What not to put here

Do not store passwords, API keys, personal credentials, or one-time task details. Keep secrets in Connections and environment. Use chat for the exact change you want now, and avoid contradictory project rules that make ordinary work ambiguous.