Skip to main content
Conversations opened from Oppy in the Firmhouse Portal sidebar and connections to Firmhouse MCP require an Agent seat for your project. Oppy in the Customer Portal editors and Workflow Builder is included on Advanced if you have permission to edit there. You do not need an Agent seat to use Oppy in these editors.

​
Who can use Oppy from the sidebar and MCP

To use Oppy from the Portal sidebar or connect to Firmhouse MCP, you need:
  • a Firmhouse user account
  • access to the Firmhouse project
  • an Agent seat assigned to you for that project
Agent seats are assigned per project. Having a seat in one project does not give you access to Oppy or Firmhouse MCP in another project.

​
Customer Portal editor access

To use Oppy in the Customer Portal template and component editors, your project must be on Advanced, and you must have permission to edit the templates or components. You do not need an Agent seat. The visual editor requires Customer Portal v2 to be enabled. Contact Firmhouse support to enable components for your project. On other plans, users who can edit templates or components see “You don’t have access to Oppy yet” and are asked to upgrade their project to Advanced. If you do not have editing permission, ask a project manager for access. You can still edit manually, preview changes, review versions, and publish if the editor is enabled and you have permission to use it. Assigning an Agent seat does not change the plan requirement for Oppy in these editors.

​
Workflow Builder access

To use Oppy to create or edit workflow drafts, Workflow Builder must be enabled for your project, your project must be on Advanced, and you must have permission to edit workflows. You do not need an Agent seat. Contact Firmhouse support if Workflow Builder is not available in your project. On other plans, users who can edit workflows see “You don’t have access to Oppy yet” and are asked to contact Firmhouse support to get access. If you can view a workflow but cannot edit it, Oppy asks you to get workflow editing permission instead. You can still create workflows from ready-made templates, edit them manually, publish, enable or disable them, review run history, and retry runs if Workflow Builder is enabled and you have the required permissions. Published workflows keep running if your plan changes or an Agent seat is removed. Losing access to Oppy prevents further requests to create or edit drafts with Oppy.

​
Assign Agent seats

Project managers can assign Agent seats to other members of their project from the Oppy sidebar. Managers can assign and remove seats when the sidebar is enabled even if they do not have a seat themselves.
  1. Open your Firmhouse project.
  2. Open Oppy from the Portal sidebar.
  3. Open Settings.
  4. Choose which project members should have an Agent seat.
  5. Save the seat changes.
After a seat is assigned, that user can start and continue Oppy conversations for the project. They can also authorize a Firmhouse MCP connection from supported agent tools.

​
Remove Agent access

Remove a user’s Agent seat when they no longer need access to Oppy or Firmhouse MCP for a project.
  1. Open Oppy from the Portal sidebar.
  2. Open Settings.
  3. Remove the Agent seat from the project member.
  4. Save the seat changes.
Removing a seat stops that user from using Oppy from the Portal sidebar and Firmhouse MCP for the project. They can still use Oppy in the Customer Portal editors and Workflow Builder on Advanced if they have editing permission.