Skip to main content

Collaboration

Glowtify is built for teams. This article covers how to invite collaborators, what each role can do, and the approval / commenting workflow inside epics.

Inviting collaborators​

From Workspace manager → Team → Invite:

  1. Enter the person's email
  2. Pick their role
  3. Glowtify sends an invitation link

If the person already has a Glowtify account, they join immediately on accepting. If not, they create an account first.

Roles​

Glowtify has two roles today, scoped per workspace — someone can be admin on one workspace and client on another.

Admin​

The default role for the person who created the workspace and for any teammate who needs to run it day-to-day.

  • Full access to everything in the workspace
  • Invite, remove, and change roles of other members
  • Connect, reconnect, and disconnect connectors
  • Create, edit, publish, and schedule content
  • Access all analytics and the activity log
  • Manage billing
  • Delete the workspace

Client​

The lighter-touch role for the client side of a workspace — typically the brand owner or stakeholder when an agency runs the workspace on their behalf. Clients are part of the conversation but don't manage the operational machinery.

  • Read everything in the workspace (campaigns, content, analytics)
  • Comment on epics
  • Approve content when an admin sends it for review (see Approvals below)
  • Cannot invite or remove other members
  • Cannot connect/disconnect connectors
  • Cannot delete the workspace or change billing

Two other roles (editor, viewer) exist in the codebase for future use but aren't currently exposed in the UI. Today you'll only see Admin and Client.

Comments​

Every epic has a comment thread. Comments can be:

  • General — on the whole epic
  • Anchored to a specific section — brief, a task, the preview
  • Threaded — replies under a parent comment

Mentions​

Type @ + a teammate's name to mention them. They get a notification in the bell at the top-right of the app, plus an email if it's important.

Resolving comments​

Comments can be marked as resolved once addressed. Resolved comments are collapsed but remain in history.

Approvals​

For teams that need sign-off before publishing, enable approvals on an epic:

  • Single approver — one named teammate must approve before the epic can be scheduled
  • Multiple approvers — all named teammates must approve (unanimous)
  • Any of several — any one of N can approve

Approvals apply at the full-epic review step — not at the individual task level. (Individual tasks have their own light-weight "approve" action to move between tasks; it's separate from the collaboration-level approval.)

Requesting approval​

From inside an epic in Review state, click Request approval. Pick the approver(s) — usually a Client when the brand needs to sign off. They get a notification with a direct link.

Approving or requesting changes​

An approver sees the full epic, including comments. Two actions:

  • Approve — epic moves to Scheduled
  • Request changes — epic stays in Review; the author sees the change request as a comment

Activity log​

Every workspace has an activity log showing:

  • Epics created, edited, approved, published
  • Team changes (invites, role changes, removals)
  • Connector changes (added, reconnected, removed)
  • Billing changes

Admins have full access to the log.