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:
- Enter the person's email
- Pick their role
- 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β
Roles are store-scoped β someone can be admin on one store and viewer on another.
Adminβ
- Full access to everything in the store
- Can invite, remove, and change roles of other members
- Can delete the store
- Can manage billing
Editorβ
- Create, edit, publish epics
- Manage connectors
- Access analytics
- Cannot manage team or billing
Viewerβ
- Read-only access to everything
- Can comment on epics but not edit
- Useful for stakeholders (managers, clients) who need visibility without write access
Depending on your plan, custom roles may be available with fine-grained permissions.
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-app + email + Slack if connected).
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). 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 store 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. Editors see actions they were involved in.
Related articlesβ
- Workspace manager β manage the team
- Edit an Epic β where comments and approvals live in the flow
- Notifications β where team actions are surfaced