FAQ: Using AI & Mason

Overview

Mason is Ressio’s built-in AI assistant. It helps your team get answers faster and complete common workflows with guardrails.

Who is this for

Builders / PMs / project teams who want faster answers and less manual work
Admins who manage access, rollout, and safety controls

When to use Mason

Use Mason when you want to:

Quickly find information across your Ressio workspace
Summarize project status, risks, and next steps
Draft content (updates, notes, scopes/specs, client-ready summaries)
Get help deciding what to do next in a workflow

How Mason stays safe (at a glance)

Permission-aware: Mason only has access to what you have access to in Ressio.
Review before changes: For actions that change data ("write actions"), you review what will happen before anything is committed.
Best practice: Start with read-only use cases first, then expand to write actions as your team gets comfortable.

FAQ

What is Mason?

Mason is Ressio’s built-in AI assistant that helps you get answers and move work forward faster—within your Ressio workspace.

Is Mason just a chatbot?

No. Mason is designed to work in Ressio so it can support real workflows—not only generate text.

What can Mason help me do?

Depending on what’s enabled in your account and your access level, Mason can help you:

Find information across your Ressio workspace
Summarize project updates and activity
Draft content (notes, updates, scopes/specs, emails)
Recommend next steps for common workflows

Does Mason follow Ressio permissions?

Yes. Mason respects the same access controls as Ressio. If you don’t have access to something, Mason can’t access it either.

Can Mason make changes in my workspace without my approval?

No. For workflows that change data ("write actions"), Mason uses a review-and-approve flow so you can confirm what will be changed before it happens.

What are “write actions”?

Write actions are steps that create, update, or change items in your workspace (for example: creating a task, updating a field, or generating a record). If a request involves a write action, you’ll be prompted to review the change.

What are the risks of using AI in project workflows?

AI can occasionally misunderstand a request or miss context. That’s why we recommend:

Starting with read-only questions and summaries
Reviewing any changes before committing
Limiting who can approve write actions until your team is confident

How should an admin roll out Mason to a team?

A simple rollout that works well for most teams:

Start with 1 admin + 1–2 power users
Choose 2–3 repeatable workflows to test
Run a 2-week pilot focused on measurable outcomes (time saved, fewer misses)
Expand access and write actions after you’ve confirmed the right guardrails

We already use ChatGPT / Copilot / Claude. Why use Mason?

General AI tools are great for writing and brainstorming, but they typically aren’t connected to your Ressio workspace in a permissioned, workflow-aware way. Mason is valuable because it’s built into Ressio with guardrails and workspace-aware access.

What about privacy and data security?

Mason is designed to respect your Ressio workspace access controls and security expectations. If your organization has specific requirements (sensitive projects, restricted roles, compliance needs), share those with your Ressio team so we can confirm the right setup and rollout plan.

How does pricing work?

Pricing may vary by plan and availability.

If you have questions about your current packaging, usage, or what’s included, contact your Ressio team for the details specific to your account.

Known limitations (important)

Mason may not always be correct—always verify critical details.
For high-impact changes, use the review step and confirm outcomes.

Still have questions?

When contacting support, include:

What you asked Mason
What you expected to happen
What happened instead (screenshots help)
Whether the request involved a read-only question or a write action