Abstract

• Origin Group = the group the author belonged to when the content was created.

• It mainly affects author ownership and collaboration, not who can view the content.

• Content access is controlled by group membership, not the Origin Group.

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

Simple rule:

Origin Group → creation and author collaboration
Group membership → who can access the content

 

What is an Origin Group?

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

The Origin Group is primarily used to manage:

• Author ownership

• Collaboration between authors

• Editing permissions

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

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

 

How Content Access Works

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

Example

1. An author in Group A creates a project.

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

3. A user in Group B can still access the project if it is shared with Group B.

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

 

How Origin Group 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 a project’s Origin Group is Group A, Author B cannot collaborate on it unless they are also in Group A.

 

Moving Authors Between Groups

When an author is moved to a different group, they lose access to projects they previously created in Create.

Example

1. Author creates projects while in Group A

2. Author is moved to Group B

3. The author can no longer see the projects created in Group A in Create.

If the author is moved back to Group A, access is restored in Create.

 

Visual Example

Project Created
        │
        │
Author in Group A
        │
        ▼
Origin Group = Group A
        │
        │
Content can still be accessed by:
Group A users ✔
Group B users ✔ (if published or 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 in 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 or published) to Group B.

• Origin Group does not block access.

 

Scenario 2: An Author Changes Groups

Situation

An author creates projects while in Group A, then is moved to Group B.

Result

• The author loses access to those projects.

• If the author returns to Group A, access is restored.

 

Scenario 3: Authors Collaborating

Situation

Two authors want to work on the same project.

Result

• They must belong to the same Origin Group.

• Authors in different groups cannot collaborate on projects across Origin Groups.

 

Quick Reference

 

Best Practices for Admins

To avoid access issues:

• Avoid moving authors between groups unless necessary.

• If an author must move groups, confirm whether they still need access to projects created in their previous group.

• Ensure collaborating authors belong to the same Origin Group.

 

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