Portal management

Portal management is the single place where you maintain everything your customers see in the customer portal: the roadmap, the answers to feature requests, the list of known issues, reported content, and the products everything is structured by. You reach it via CRM → Portal management.

The page is split into tabs. The selected tab is stored in the address bar, so you can bookmark it or pass it on.

What can I do here?

• Roadmap content: create, edit, publish and withdraw roadmap cards
• Feature requests: review submitted customer requests, link them to cards or decline them
• Bugs: manage reported and internally recorded issues and assign affected customers
• Moderation: review and resolve content reported by customers
• Source: review issues that were marked for the roadmap as candidates
• Products: maintain the product list that the roadmap and bugs are structured by

Step by step

Create and publish a roadmap card

As long as no card is published, the roadmap in the customer portal stays empty. Creating a card is therefore usually the first step.

1. Open CRM → Portal management. You land on the Roadmap content tab.
2. Click New card. The editor opens on the right-hand side.
3. Under Customer-facing content, choose the Source language - the language you are writing the card in.
4. Enter a Title and a Description. Word both so that a customer understands them without internal knowledge.
5. To offer the card in the other language as well, click that language in the language bar above and write title and description there. A language without a title is not saved - it simply stays open.
6. Choose the Product the card belongs to. Customers filter the roadmap by it.
7. Under Source & status, set the Status (see "Values & statuses" below).
8. Directly underneath is the Release quarter. Choose year and quarter. It is required for status "Released"; otherwise you may leave it empty.
9. Under Visibility, switch on Show on the roadmap if the card should be visible to customers.
10. Click Create card.

Offer a card in another language

Title and description are kept per language, currently German and English. Open the card, click the language you want in the language bar under Customer-facing content, and write title and description there. A language that is still empty is marked "missing" in the bar.

Where a translation is missing, the customer does not see an empty card: they read the source-language version, with a note above it saying the card is not available in their language yet. A card in the wrong language is readable; an empty one is a dead end.

The source language is the version that stands in. It is therefore mandatory, and publishing checks title and description in exactly that language.

Add a card to the roadmap or withdraw it

You do not have to open each card for this: every row in the list carries Add to roadmap or Remove from roadmap on the right. Withdrawing asks for confirmation, because the card disappears from the customer portal immediately. Content and history are kept.

Review candidates from the issue tracker

The Source tab shows issues from our issue tracker that were explicitly marked for the roadmap. A candidate is not a card yet: it appears nowhere in the customer portal until you create and publish a card for it yourself.

1. Open CRM → Portal management and switch to Source.
2. The state of the source is always shown at the top: when the last successful sync happened, or that nothing can be fetched right now.
3. Click Sync now to pull in newly marked issues.
4. Every candidate shows its internal title, a suggested status and a suggested quarter. Both are suggestions; the decision is made when you create the card.
5. Use the search field to filter long lists. The search term is part of the address and can be shared.
6. The Intake column tells you whether a candidate already became a card: Open, Created as a draft or Published. Only open candidates offer the Take in button, so nobody takes the same candidate in twice.

Turn a candidate into a card (intake assistant)

Click Take in next to an open candidate. The assistant walks you through four steps, and nothing is stored until the last one: abandon it halfway and there is no card at all, neither visible nor as a draft.

1. Candidate: you see the internal title, the suggested status and the suggested quarter. The internal title is explicitly marked "Internal only". It is not carried over into the card - not into the title, not into the description, not into the preview.
2. Category: choose the product the card sits under in the customer portal. Without a category you cannot continue, and a card without a category cannot be published either.
3. Content: write the customer-facing title and description, one per language. The source language needs both; a further language can be added later.
4. Preview: you see the card the way a customer reads it, in German or in English. If the chosen language has no text yet, the preview shows the source language with a note - exactly as the customer portal does. Then you decide: Publish puts the card into the portal, Save as a draft only creates it without showing it.

Publishing is reversible. You can withdraw the card later via Remove from roadmap; it keeps its identity, so links and notifications still resolve.

Bug reports never appear here. An issue marked as a bug is refused even when someone marked it for the roadmap. Those issues are listed below under Refused, together with the label that blocked the intake, so you can see that it was seen and deliberately not taken over.

Add a history entry

Lasting information about a card belongs in the History, not in comments. Open the card, write your text under History and click Add entry. The entry appears as an official message from SELLERLOGIC.

Moderate a report

1. Switch to the Moderation tab. It lists all open customer reports.
2. Read the reason and check the reported content.
3. Click Resolve once there is nothing left to do. The report disappears from the list; the reported content itself stays unchanged. If it needs to be removed or edited, do that first on the matching tab.

Create a product

1. Switch to the Products tab and click New product.
2. Enter a Name and an Order (lower numbers come first).
3. Click Create product. The product is then available in the selection lists of cards and bugs.

Products cannot be deleted, only deactivated. A deactivated product can no longer be selected, but cards and bugs already assigned to it keep it. That way no assignment is lost silently.

Fields explained

Values & statuses

portal_card_status (status of a roadmap card)

• Planned: Noted down, work has not started yet.
• In progress: Currently being implemented.
• On hold: Work is paused for now.
• Up for release: Finished, waiting to be shipped.
• Released: Shipped. The card moves into the release archive and is filed there under its release quarter. Only for this status is the quarter mandatory.

portal_card_origin (origin of a card)

• Standalone: Created by you in the portal, without a source.
• From feature request: Grew out of a customer request.
• From Paperclip task: Points at an internal task.
• Taken in from a candidate: Created from a marked issue through the intake assistant.

Origin and internal reference are visible to you only. Customers never see them.

Frequently asked questions

Why is the roadmap in the customer portal empty even though I created cards?
Cards only appear once Show on the roadmap is switched on. Check the "Visibility" column in the list: if it says "Draft", the card is not published yet.

Why can I not publish a card?
Publishing needs three things: a title and a description for customers - both in the source language - and a category. If any of them is missing, the editor or the intake assistant says so and the button stays disabled. Drafts may sit without a category; they just do not become visible that way. Older cards that were published before the rule and carry no category stay editable: you can still change their status, their wording and their quarter, and you can add the category at any time. Taking the category away from a published card is refused.

Do I have to write every card in both languages?
No. Only the source language is mandatory. Without a translation a customer reads the source language together with a visible note. You can add the second language at any time.

Why is the "Source" tab empty?
There are three different reasons, and the note at the top of the tab names the one that applies: the source is not set up, no sync has run yet, or the issue tracker did not answer. Only when it reports a successful sync does an empty list actually mean "nothing is marked".

An issue is marked but does not show up as a candidate. Why?
Check under Refused. If the issue carries a bug label, it is blocked from the customer-facing roadmap. If it is not listed there either, no sync has run since it was marked.

Why does status "Released" require a quarter?
Because the release archive is grouped by quarter. Without a quarter the card would not know where to be filed.

Why can I not enter a date, only a quarter?
Because the roadmap deliberately does not promise day-level accuracy. Customers see quarter and year.

Where are the old menu entries "Portal bugs" and "Roadmap portal"?
Both have been merged into this single page. They are now the Bugs and Feature requests tabs. Your old bookmarks keep working and open the matching tab.

Why do I not see the "Moderation" tab, or only a notice?
Moderation requires its own permission. Please contact someone with administration rights.

Related topics

• Roadmap portal: feature requests
• Known issues (bug tracker)
• Customer Portal: Roadmap & Sign-in