Skip to main content
Experience collaboration is separate from visitor delivery. Owners, folders, tags, review decisions, and internal comments help your team prepare a draft; they do not rewrite a revision, deployment receipt, analytics event, or customer progress record.

​
Assign and organize drafts

Open an Experience and select Collaboration to assign a current workspace member, choose a folder, and add up to 10 lowercase tags. The Experience list can filter by owner, review status, folder, and tag. Those filters stay in the URL, so a filtered workspace view can be bookmarked or shared. Owners and admins can select up to 50 Experiences and change their owner, folder, or tags together. Each change checks the current collaboration version. If a teammate edited any selected Experience, Puntego stops the whole batch without applying a partial result.

​
Review an immutable revision

The review workflow is Draft → In Review → Approved or Changes Requested. A non-Draft decision is bound to the latest immutable revision. Saving a new definition resets review to Draft, ensuring an earlier approval cannot silently cover new visitor-facing content. Every active workspace member can add a revision-specific comment. Comment authors can resolve or reopen their own comments; workspace owners and admins can manage any comment. Puntego prevents approval while a general comment or a comment on the revision under review remains open. An older revision’s open comments stay visible without blocking a newer immutable revision. Comments are internal and never included in visitor delivery. They remain until the Experience or workspace is permanently deleted, retain the author’s display name if that member leaves, and are included in workspace data exports.

​
Duplicate safely

Duplicating creates an independent Draft at revision 1 from the latest typed definition. It copies the description, folder, and tags and assigns the new draft to the teammate making the copy. It does not copy comments, deployments, analytics, visitor progress, action claims, or other runtime state. Duplicate requests are idempotent: retrying the same request cannot create an extra copy.