Landinker

Groups in Landinker

What are Groups?

Groups in Landinker are collaborative workspaces where users can organize, create, and manage landings, components, and shared resources.
A group can represent a company, team, or project, centralizing pages, users, and permissions in one place.

How do they work?

• Each user can belong to one or more groups.
• Within a group, users share resources and landings.
• Access and possible actions depend on assigned roles and permissions.
• Groups provide organizational independence, so one group's resources never interfere with another's.

Example:

• A user can be in the group "Startup A" with administrator permissions.
• At the same time, they can be in the group "Freelance Project" as a contributor with limited permissions.

Getting started

Upon creating a group, its Overview displays a Getting started checklist (visible to the Owner) that guides setup: customizing the palette, creating your home page, publishing a landing, and inviting your team. Each item is checked off automatically upon completion, and the checklist disappears once everything is done (or if you hide it).

The home page is the landing living at the / route: it is what visitors see when accessing your domain without typing any path (and where people arrive from Google or shared links). If not created, your site root displays the 404 page. From the checklist, "Create home page" opens landing creation with the / route pre-filled.

User management

• Users are invited to the group via email.
• Each user has an assigned role determining what they can do.
• User management is handled from the Group Settings section.

Possible actions:

• Invite users.
• Change roles.
• Revoke access.

Permission and role management

Permissions control what a user can do within a group.

Roles

• Owner: full control of the group (content, members, settings, and subscription).
• Editor: edits landings, blog, and products; views metrics.
• Landing Editor: edits landings and blog; views products and metrics.
• Product Editor: edits products; views landings, blog, and metrics.
• Viewer: read-only access to landings, blog, products, and metrics.

Full details on what each role can do (complete matrix) are in Roles and permissions. To invite team members and assign roles, see Members and invitations.

Common use cases

1. Small startup:

   • Admin invites their team and configures access.
   • Editor designs and tweaks landings/products.
   • Viewer is an external client who only checks results.

2. Marketing agency:

   • Each client is an independent group.
   • Agency administrators have full permissions.
   • Clients hold the Viewer role to track progress and metrics.

Summary

Groups in Landinker allow:

• Organizing users and resources in a single workspace.
• Defining roles with clear, hierarchical permissions.
• Facilitating collaboration across teams.
• Maintaining independence between different projects or companies.

Note: Legacy role names may exist in older integrations or migrations. In Landinker's current experience, the roles used are Owner, Editor, Landing Editor, Product Editor, and Viewer.