Walls, sharing and access

There are three ways to let other people see a project:

Way	Who	Needs an account?	What they see
Public wall	Anyone with the link (KOLs, clients)	No	A read-only feed of the project
Public campaign report	Anyone with the link	No	One campaign's KPIs and top posts (see Campaigns)
Guest	A named email outside your team	Yes, a free Lantfly account	The whole project, as viewer or analyst

Inside your own organization, project roles decide what each member can do.

Public wall

A wall is a read-only page of the project's feed for people without an account: a moodboard for KOLs, a live feed for a client. Hidden posts stay hidden.

1. Open the project's Settings tab and find Public wall.
2. Click Create a share link and copy the link. It looks like https://lantfly.com/wall/<token>.
3. Send it to the people who should see the wall.

Visitors can filter by platform, sort by Newest or Top, and search the text.

• New link replaces the link; anyone with the old one loses access.
• Stop sharing turns the wall off. You can share again later; it makes a new link.

The link is shown once

Lantfly only stores a hash of the token, so the link is shown only right after it is made. To copy it again, make a new link. Only project managers see and manage walls.

The wall's data is also available without authentication at GET https://lantfly.com/api/public/walls/{token}, with platform, sort (recent or top) and q (2 to 100 characters). It allows 120 requests per minute, and 20 searches per minute per IP address.

Share a project with a guest

Agencies use this to give a client access to one project, without adding them to the team.

1. Open the project's Access page and find Share with a client.
2. Enter the guest's Email and pick a Role:
   • Viewer reads everything in the project;
   • Analyst also tags, verifies and comments mentions.
3. Click Share. The guest receives an email.

What happens next:

• If the email already belongs to a verified Lantfly account, the project is shared right away.
• Otherwise the share waits (14 days by default). The link in the email lets the person sign up or sign in with that email and claim the project, even while public sign-up is closed.
• The guest opens the project from their personal account, under Social listening → Shared with me. When they act for an organization, they need to switch to their personal account first.
• Guests never see your billing, your team or your other projects.

The Shared with list shows each guest's role and status (Invited or Opened). Change the role at any time, or Revoke access, which takes effect on the guest's next request.

note

Guests do not receive the project's alerts. Public wall and report links are only visible to managers, so a revoked guest cannot keep a working public link.

Project roles

Role	Can
Viewer	Read everything in the project: mentions, analytics, creators, campaigns, reports, exports
Analyst	Viewer, plus label mentions (hide, sentiment, intent, attributes), verify mentions, work leads, see raw data
Manager	Analyst, plus settings, sources, Collect now, campaigns, alerts, reports, sharing

Deleting a project takes the listening.manage permission on the account, not only the manager role.

How members get a role

• On a personal account, and for owners and admins of an organization: Manager of every project.
• Other members, by default: every project, with the role their team role gives (listening.manage makes them managers, listening.view viewers), or a higher role given on a project.
• Owners and admins can give a member a role on one project on its Access page, under Team members.

Restrict projects per member

On the Team page, owners and admins can turn on Restrict listening projects per member. Members then see only the projects they are given a role on, with exactly that role. Owners and admins still see everything.

When restriction is on, alerts by bell and email only reach the people with a role on the project.

Agencies and white label

Agencies can run a workspace per client and share projects with client users. Reports, public reports and walls carry the agency's branding when white-label branding is set. See Agencies and Roles and permissions.

Activity log

Sharing, role changes, revocations, project role assignments and the restriction switch are written to the activity log of the account that owns the project. Every change a guest makes on the shared project is logged too.

With the API

Endpoint	Purpose
POST /listening/projects/{project}/share	Wall on (a new token, returned once as share_token) or off (enabled: false)
GET /listening/projects/{project}/access	Your role and can (view, analyze, verify, manage)
GET /listening/projects/{project}/members	Members with their project role, guests, and restrict_projects
PUT, DELETE /listening/projects/{project}/members/{user}	Give or remove a member's project role (owners and admins)
POST /listening/projects/{project}/guests	Share with an email: email, role (viewer or analyst). Always 202
PATCH, DELETE /listening/projects/{project}/guests/{guest}	Change a guest's role or revoke
GET /listening/shared	Projects shared with you (personal account only)
POST /listening/shared/claim	Claim a share with the token from the email
GET, PUT /listening/access-settings	Read or set restrict_projects