Cycle's help center
LegalCompany
  • 🧱Core Documentation
    • βš™οΈFirst Workspace Setup
    • πŸš€Capturing Feedback
    • ⚑Processing Feedback
    • πŸ“ŠAnalyzing Data
    • 🀩Closing the Loop
  • πŸ“šGuides
    • πŸ”—Integrations
      • HubSpot
      • Salesforce
      • Linear
      • GitHub
      • Notion
      • Slack
      • Intercom
      • Zapier
      • Call recording
      • Email
      • Chrome extension
      • Gong
      • Zendesk
      • Modjo
    • πŸ‘·Customer Sync
      • Customer Data Ingestion
      • Exporting Salesforce Customer data
      • Exporting HubSpot Customer data
    • 🏷️Properties
    • πŸŒ†Views
    • πŸ“AI-powered editor
    • πŸ””Notifications
    • πŸ“’Release Notes & Public Changelog
  • πŸ“–Cycle Glossary
  • πŸ₯³Latest Features
    • 🧠Custom Prompts
    • πŸ“‚Product Areas
    • πŸ“ŠCycle Dashboards
    • πŸ€–Cycle Ask – Your On‑Demand Product Analyst
Powered by GitBook
On this page
  • Maker vs collaborator
  • Customer vs assignee

Was this helpful?

  1. Setup

Manage workspace members

Last updated 1 year ago

Was this helpful?

Maker vs collaborator

There are 2 roles you can have in Cycle.

  1. A β€œMaker” can create insights, create and edit views, change other members' roles, use advanced features like transcripts, and manage billing. A maker can add unlimited collaborators for free.

  2. A β€œCollaborator” can do everything else. This includes creating docs, editing docs, updating property values, and more. Collaborators cannot edit the workspace setup (, , ,...).

Makers can edit roles in the workspace’s settings.

Here's how πŸ‘‡

Customer vs assignee

Customer

The person giving the feedback (could be external or internal like a colleague for instance).

Customers are currently only notified when you have a Slack connection with them in the thread or when an initiative changes category (e.g. not started -> started). You can customize the notifications you send to them in your Slack integration in Cycle.

Assignee

The person in charge of closing the loop with the customer. They are Cycle users.

The PM in charge of the feature is not supposed to be the assignee. If needed, you can create a "product squad" property to create some views linked to this PM/Squad particularly

You can update the default assignee in your Workspace settings > Members. This person will be the fallback assignee for all situations with no assignee, like new forms coming through Zapier.

βš™οΈ
🎭
integrations
views
workflows