Public portals
Open a portal to anyone with the link, show updates as a timeline, and publish posts automatically.
- PlanPro or Enterprise
- WhoOwners and admins
Open a portal to anyone
A portal is for invited guests by default. Only the people you invite can open it, and they sign in first. A public portal is open to anyone with the link. Visitors read your published updates without signing in and can send feedback. Use one for release notes, a changelog, or a project that has a community around it.
Public portals need a Pro or Enterprise plan.
Every portal is one of two kinds. A Client portal is for working with another company. Invited guests follow progress, talk in Discussion, get files, and approve or request changes. An Updates portal announces and shows progress, either to invited people or to anyone with the link, and can take feedback when it is for a product. In Settings, Who it's for shows the kind of an existing portal, and an Updates portal also shows Who can open it: Invite only or Anyone with the link. Choosing another kind asks you to confirm, then resets the sections, layout, review actions, and discussion to that kind's starting options. It keeps the name, projects, and branding. After that the switches are yours, and the kind stays as you chose it.
Only owners and admins can change access. To open a portal, choose Anyone with the link, check the Address, and select Make public. You confirm first, and everything already shared on the portal becomes visible to anyone with the link. Guests you already invited are kept, and they can sign in again if you switch back to Invite only, which also asks you to confirm.
Choose the portal address
A public portal lives at /p/your-name on the Project Feed site. Choose the name in Settings, under Who it's for, as the Address. Use 3 to 48 lowercase letters, numbers, and hyphens. The field tells you if a name is taken or reserved. Each name belongs to one portal across all workspaces.
Select Copy beside Address, or Copy link in the portal header, to share it. Select Change address to save a new name. Changing the address stops every link people already have from working. The older /portal/ link of a public portal sends visitors to the public address.
What visitors see
Visitors see the portal's name and logo in its menu, next to the sections you turned on. The description and links sit in the sidebar. With the menu collapsed or on a phone, they sit at the top of the updates instead. They can read updates, open shared docs, and send feedback. Docs are view-only, even if you shared them with comment or edit access.
Visitors cannot approve updates, request changes, react, comment on updates, or join a discussion. A public portal has no signed-in guests, no guest list, and no invitations. Insights shows visits and update views instead of activity for each guest.
A public portal stops showing to visitors if the workspace leaves Pro or an admin turns public portals off. Visitors see a message that the portal is not available. Admins see a banner on the portal that says why. Nothing is deleted, and the portal comes back when the cause is fixed.
Choose the sections
In Settings, What people can do turns each part of a portal on or off. On an invited portal, Approve or request changes adds review actions to updates you ask a decision on. Send feedback is the form for bug reports, ideas, and questions. Join the discussion is one shared conversation for everyone on the portal. See docs shows the docs you share, See files shows the files attached to your updates, and Download originals lets people download full-size media.
Every Updates portal has Comment on updates, which lets guests comment on each update and pin comments on images. Turning it off hides those comments without deleting them. On a Client portal, comments are always on, because that is how guests review work. A public portal also has Hold first comments in place of review actions and the discussion. A section that is off disappears from the portal. Edit form shows beside its switch while Send feedback is on.
Picking a type under Who it's for resets these switches to that type's defaults. You can change any of them afterwards. On an invited portal with Send feedback on, signed-in guests send reports without the human check that visitors complete.
Show updates as a timeline
An Updates portal shows its updates as a timeline. A Client portal uses a review inbox instead: a list of updates with a reading pane. The timeline opens with the newest update featured, then lists older ones as cards with their first image and opening lines, which suits release notes. Select a card to read the whole update.
Each update has its own link, in the form /p/your-name/updates/12. Select Copy link on an update to share it. The link opens that update, with its title and a short excerpt in the preview when it is shared. Approve or request changes is for invited portals and is never available on a public portal.
Lead with your latest release
A post can carry release details: a version, a type of Release, Beta, or Alpha, what it works with, and a download link. When you share such a post, its portal copy shows them as a chip, a Works with line, and a link that opens in a new tab.
On a Timeline portal, the newest shared Release is featured at the top as Latest release, with a Download button, even when newer updates exist. If no Release has been shared, the newest Beta or Alpha is featured instead as Latest beta or Latest alpha. Public visitors also see the latest version and its download link beside the description and links; invited contacts see the featured update but not that line. Updates you remove from the portal are never featured.
The RSS feed includes the version, type, and download link in each release item, and shared update links show the version in their preview title. Changes to a post's release details, including removing them, show on its portals right away. Text and file edits update public portals automatically. Invite only portals keep their shared copy until you select Update.
Comments and moderation
On a public portal, anyone can read the comments under an update. Members can write comments, reply once to a comment, edit or delete their own, and react with one of six emoji. Visitors who are not members see a prompt to join. Members who left or were blocked can read but not write. Comments are plain text up to 4,000 characters. People see a member as @username, and your team's replies carry a Team label.
By default a new member's first comment waits for your approval. They see it with Waiting for approval, and nobody else does. Once you approve it, their later comments show right away. The approval lasts while that comment stays published. If you hide it or they delete it, their new comments and edits wait for approval again. In Settings, turn off Hold new members' first comment, under What people can do, to publish every comment immediately.
Owners and admins open the Feedback tab and select Held to see comments waiting for approval. A badge on Held and on Feedback shows how many are waiting. Each comment lists the update, the author, and the text. Select Approve to publish it or Reject to keep it hidden. Select Block to stop the member from commenting and reacting, and confirm. Choose Also hide everything they posted and remove their reactions to hide everything they wrote and remove their reactions. Unblock them from Members.
To reply as your team or hide a published comment, open the menu on a post's card in Shared and select Member comments, or open the post and use the panel beside it. Hiding a comment also hides the replies under it.
To turn comments off, switch off Comment on updates under What people can do in Settings. The comments section disappears from every update, and your existing comments return if you turn it back on.
Publish posts automatically
Turn on Auto-publish under Portal to add new published posts to the portal without sharing each one. Open Auto-publish sources and choose the Projects to publish from. They must be projects included in the portal. To publish only some posts, add tags under Only posts with these tags. A post needs at least one of them. Leave the tags empty to publish every post from those projects. Removing a project from the portal removes it from Auto-publish too. If none of the selected projects remain, Auto-publish turns off.
A post is added when it is published, or when a matching tag is added to a published post. Posts that were already published when you turned Auto-publish on are not added. Publishing a new version of a post refreshes its copy in the portal. A post you removed from the portal stays removed.
Posts are shared as the admin who enabled Auto-publish. If they leave the workspace or lose that permission, Auto-publish stops and the portal shows a notice. An owner or admin can update the settings and select Save and re-enable to continue under their own publishing access.
Add links, an RSS feed, and search listing
Add up to six links to a portal, such as a website, a Discord server, or a download page. In Settings, under Basics, select Add links next to Portal links, enter a label and an https address for each one, and select Save links. Links show in the portal sidebar, and on a phone behind the portal name at the top. Each link shows its site's icon. Project Feed fetches the icon once when you save, so guests never load anything from the linked site.
A public portal with Updates on also has an RSS feed at /p/your-name/feed.xml. It lists the 50 latest updates. Visitors find it under Subscribe in the portal sidebar, or behind the portal name on a phone, alongside the email signup when Email updates is on.
Public portal and update links include a title, description, and large preview image. Updates use an available media thumbnail; the portal uses media from its latest visible update. When no usable image is available, Project Feed creates a preview card from the title and description.
Search engines are asked to skip public portals. To let Google and others list the portal, turn on Let search engines find it under Portal. The portal, its updates and its shared docs are then added to the sitemap at /p/sitemap.xml, and it can take a few weeks to appear in results. Turning it off removes them from the sitemap and asks search engines to stop listing them.
Turn public portals off for a workspace
Owners and admins can turn off Allow public portals in workspace settings, under Permissions. While it is off, nobody can make a portal public, and existing public portals stop showing to visitors. Their settings and reports are kept. Turn it on again to bring them back.