A team start page nobody has to remember to visit

Every internal portal dies the same way

Someone builds the portal. It is good. It goes out in an all-hands, people say nice things, and a handful of them bookmark it. Week two, traffic is a third of week one. Week six, the only visitors are the person who built it and one very conscientious accountant. Nothing was wrong with the page. The problem is that visiting it was a decision, and it competed with the fifteen other decisions in someone's first ten minutes.

The wiki home page fails for the same reason, one layer deeper: people arrive at the wiki through search results and never see the front door at all. Then the links on the front door go stale, which confirms everyone's suspicion that it was never worth visiting.

The most-visited page of a workday is already open

Count how many times a day you open a new tab. Every task begins there — every search, every jump to a tool, every context switch. A start page you have to remember to visit will lose; a start page that is already open cannot.

The Linksley extension can make your boards the new-tab page in Chrome, Edge, Firefox and Opera. It renders from a local cache, so it is on screen before you have finished typing, and it is searchable, so the fastest path to a link is the one people already use: new tab, type three letters, hit enter. Nobody has to change a habit, which is the only reason internal tooling ever sticks.

A start page holds more than links

Boards take text blocks, checklists and calendars, which is most of what an actual start page is for. A text block gives a link context — which of the two dashboards is the real one, who to ask when it breaks. Checklists support a recurring cadence, so the Monday reporting run or the end-of-month close reappears on its own instead of living in one person's head.

Calendars come in as read-only ICS feeds from the calendar you already use, so the team's shared schedule sits next to the tools without anyone maintaining a second copy. It is a front page, not a project manager: due dates and standing rituals belong here, individual task assignment belongs in whatever tracker you already run.

• Text blocks for context, ownership and short instructions
• Checklists with a recurring cadence for weekly and monthly rituals
• Read-only team calendars from ICS feeds
• Categories and one level of subcategories to keep a long board scannable

Making it the same page for everyone

An admin can mark boards as required. Those boards land on every member's new tab when they join and cannot be removed, so the start page is genuinely shared rather than a suggestion. People are still free to keep their own private boards alongside it; the required ones simply do not go anywhere.

On the Business plan the whole surface is white-labeled: your logo on the app, the extension and the new tab. For an agency or a company placing staff, that is the difference between the team's first screen of the day carrying your brand and carrying a vendor's.

Where this is not the right answer

A start page is a front door, not a knowledge base. If what you actually need is long-form documentation with version history, keep your wiki and put the three pages people need on the board. And two limits worth knowing before you roll it out: there is no Safari extension, and while the web app opens on a phone browser, the new tab replacement is a desktop-browser feature.

Setting it up is short. Install the extension, allow it to take over the new tab, build one board with the eight links everyone opens daily, then mark it required. See new tab page for work for the layout most teams settle on.