Overview

• Authors must have an Origin Group value in the Content Management System (CMS) as this controls access to projects in Create.

• It affects author ownership and collaboration, not who can view the content (published scenario).

• Content (scenario) access is controlled by Group membership, not the Origin Group.

• If an author moves to another Origin Group, they will lose access to projects they created in their previous Origin Group.

Simple rule:

Origin Group → project creation and author collaboration
Group membership → who can access the content (published scenario)

 

What is an Origin Group?

An Origin Group is automatically assigned to content when it is created. It reflects the Origin Group the author belonged to at the time of project creation.

The Origin Group is primarily used to manage:

• Author ownership

• Collaboration between authors

• Project editing permissions

It does not control who can view the content (scenario) on the WorkLink App.

Think of the Origin Group as the content’s place of creation, not its scenario visibility setting.

 

How Content (Scenario) Access Works

Users can access published content (scenarios) if they belong to a group in which that content is available/published to. The Origin Group does not prevent users from viewing content (scenarios) on the WorkLink App, if they have access through their Group membership.

Example

1. An author whose Origin Group  is Group A creates a project and publishes the scenario.

2. The project's Origin Group becomes Group A.

3. A user in Group B can still access the content (scenario) if the scenario is shared with/published to Group B.

Even though the project originated in Group A, users in Group B can still view it.

 

How Origin Group Membership Affects Authors

While Origin Group does not control content visibility, it does affect authors and collaboration.

Authors can only collaborate within the same Origin Group

Authors can only collaborate on projects with other authors who belong to the same Origin Group.

Example

If an author’s Origin Group is Group A, Author B cannot collaborate on the project unless their Origin Group value is updated to Group A.

 

Moving Authors Between Groups

When an author's Origin Group value is changed, they lose access to projects they previously authored within WorkLink Create.

Example

1. Author creates projects while their Origin Group is Group A

2. Author's Origin Group is updated to Group B

3. The author can no longer see the projects created while their Origin Group was Group A in Create.

If the author's Origin Group is changed back to Group A, access to projects is restored in Create.

 

Visual Example

Project Created
        │
        │
Author's Origin Group is Group A
        │
        ▼
Project's Origin Group = Group A
        │
        │
Content (scenarios) can still be accessed by:
Group A users ✔
Group B users ✔ (if published to/shared with Group B)

Origin Group does not limit access to the published scenario, it only identifies where the project originated.

 

Common Scenarios

Scenario 1: A User Accesses Content from Another Group

Situation

A project was created by an author whose Origin Group is Group A, but a user belongs to Group B.

Result

• The user can access the content (scenario) on the WorkLink App, if it is available (shared with or published to) to Group B.

• Origin Group does not block access to the content (scenario).

 

Scenario 2: An Author's Origin Group Changes

Situation

An author creates projects while their Origin Group is set to Group A, then their Origin Group membership is updated to Group B.

Result

• The author loses access to those projects in Create.

• If the author's Origin Group reverts to Group A, project access in WorkLink Create is restored.

 

Scenario 3: Authors Collaborating

Situation

An author with Group A as their Origin Group creates a project in WorkLink Create and wants collaborate with an author whose Origin Group is Group B.

Result

• The author with Group B listed as their Origin Group is unable to edit the projects as authors cannot collaborate unless they belong to the same Origin Group.

• Update the Origin Group value to Group A for the author with Group B as their current Origin Group to  to enable collaboration.

 

Quick Reference

 

Best Practices for Admins

To avoid access issues:

• Avoid updating the Origin Group membership for authors unless necessary.

• If an author must update their Origin Group membership, confirm whether they still need access to projects created in their previous Origin group.

• Ensure collaborating authors belong to the same Origin Group.

 

Related article: CMS: Understanding Origin Group for Authors, Admins, and Scenarios