Portal and boards

The portal's address#

A workspace's portal lives at its slug's subdomain: for the slug acme, acme. followed by the portal domain. Settings → General shows the address, and Portal, in the dashboard's menu, opens it. After an owner changes the slug, the old address sends visitors to the new one, and no other workspace can take it.

Boards#

Boards sort posts by theme, such as "Feature requests" or "Bugs". Your team manages them under Boards:

• Name, Slug and Description: a board's page on the portal is /boards/<slug>, with its description, in Markdown, at the top.
• Color: the dot next to the board's name.
• Visibility: public, or private for your team only. Customers never see a private board or its posts.
• On the roadmap: whether the board's posts may show on the portal's roadmap. See Roadmap and changelog.
• Order: the arrows move a board up or down the portal's list.
• Delete: the board and its posts go to the Trash and leave the portal. You can restore them for 30 days, then they're deleted for good.

The Free plan has up to 3 boards, not counting the trash.

Posts#

A post is one request: a title, a description in Markdown, and up to 4 images. People write one with New post, on the board they choose. As they type the title, the portal shows up to 5 similar posts, so they can vote for one of those instead.

• Status: Open, Under review, Planned, In progress, Completed or Closed. A new post is Open, which the dashboard calls Pending. Your team changes the status from the post's page in the dashboard, with an optional note, and the post shows the change and its note.
• Edits: a post's author changes its title, its description and its images with Edit post, for 24 hours after posting. From then on only your team edits it, from the post's page in the dashboard, at any time. A post whose title or description changed says edited, and a new title gives it a new address: the old one leads there. An author's edit is screened as a new post is: see Moderation.
• Tags: your team's labels. Selecting one lists the posts that have it.
• Votes: one per person. Voting again takes the vote back.
• Followers: authors, voters and commenters follow a post, unless they stop with the Following button. Followers hear when it changes status, gets a comment or is merged. See Notifications.
• Comments: in Markdown, with up to 4 images each, and replies one level deep. People like comments, and edit or delete their own; deleting a comment removes its replies. Your team's comments carry a Team badge, and your team can pin one comment to show first. Your team's internal notes never show on the portal.

Images are PNG, JPEG, GIF or WebP files of up to 10 MB. Swingback re-encodes them, which removes their metadata, such as where a photo was taken.

Your team can make a post private from its page in the dashboard: only your team and its author see it then. When your team merges a duplicate into another post, its votes move there, and its address leads there.

Sorting, filters and search#

The portal lists all posts, or one board's. People sort them by:

• Trending, the default: recent activity first. A post's creation, votes and comments count, each half as much for every 72 hours of age.
• Top: the most votes first.
• Newest or Oldest.
• Best match, while searching.

They filter by status and by tag. Search looks through titles and descriptions in the workspace's default language, ignores accents, and forgives typos in titles.

Languages#

The portal speaks each visitor's language: English, French, German, Spanish, Italian, Portuguese or Dutch. It answers in the language their browser asks for when that is one of these, and in your workspace's default language otherwise. A menu at the foot of every page lets a visitor choose another one, which holds on your portal at their next visits.

The portal's own words follow the reader: buttons, labels, statuses, dates. What people write stays as they wrote it, unless you turn on Translate posts and comments: each reader then has a post, and the comments under it, in their own language, beside the original (see AI features). Either way, the page where a post is written says whether posts are translated. Your boards' names and your changelog stay as written. A signed-in reader who would rather read everything as it was written says so on their Account page, with Read posts and comments in my language.

You set the Default language under Settings → General. Besides the visitors whose language the portal doesn't speak, it serves the changelog's RSS feed, the emails to people whose language isn't known, and the way search matches words. The dashboard's own words are in English; with Translate posts and comments on, each member reads both in their browser's language.

Signing in#

People sign in to post, vote, comment or follow. The portal's Sign in page offers:

• Email: they get a 6-digit code, valid for 10 minutes, and a link that signs them in too.
• Google or GitHub, when the page shows them.
• Continue with Acme, with your workspace's name, when you set up single sign-on through your own product. See Signing in your users.

A portal account is for your portal only: it gives no access to your dashboard or to other workspaces' portals. Signed-in people get notifications on the portal, and choose their emails on their account page.

Team members can sign in to the portal with their work email. There they act as your team: they see private boards, everyone's names and a hidden roadmap, and nothing they write waits for review.

Guests#

With Guests on, under Settings → General, people write without signing in: they choose Continue as a guest on the sign-in page, with an optional name and email. Only your team sees that email, and it signs nobody in.

Guests post, comment, vote and follow. They pass a security check (Cloudflare Turnstile) before each post and comment, and can't attach images. By default, their posts and comments wait for your review: see Moderation. A guest who signs in later, in the same browser, keeps what they wrote.

Names on the portal#

Names on the portal, under Settings → General, decides what the portal shows of the people who write:

• Shown: posts and comments show their author's name and picture.
• Hidden: they say "a customer", "a guest" or "a team member" instead.

Either way, your team sees everyone in the dashboard, people always see their own name, and the portal never shows an email address.