Team Page
The Team Page introduces a team’s scope, shows employees how to prepare a useful request, and surfaces current people and events. Use it to help colleagues find the right route without guessing who handles what.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Corporate facilities and workplace services · Retail and frontline operations · Healthcare administration · Higher education operations
Overview
The Team Page is a single-page orientation template for introducing a team and helping employees find the right next step. Its fictional Northstar Workplace Support example opens with a short team introduction, then distinguishes shared-workplace questions from people-related support, company-wide policies, and open roles. It also gives employees a practical sequence for preparing a request: identify the location, describe the need and timing, add relevant context, and use the currently published route.
Use this page when employees need a clear overview of a team’s remit, a concise way to prepare a question, and a place to find current team details or events. The team-member directory and calendar are connected sections, not static sample lists; configure their correct sources and check access for the intended office and frontline audiences. Confirm the team owner, correction route, scope, and contact guidance before publishing. Treat the Northstar copy as illustrative, not as a service commitment or verified local process.
This template is not a substitute for a detailed service catalog, authoritative policy, emergency procedure, or sensitive case intake form. Link readers to the organization’s established routes for those needs, including local safety reporting for urgent concerns. Keep the page focused on orientation, and avoid repeating policies or inventing response times. Review it when responsibilities, audiences, working arrangements, directory data, or event sources change; stale contact guidance can send employees to the wrong place.
Standards & compliance context
- The template does not establish legal compliance or replace organization-specific policy, safety procedures, or regulatory guidance.
- For urgent safety concerns, retain a clear direction to the location’s established emergency and safety reporting process rather than routing them through a general team request.
- Follow organizational privacy and information-handling rules; the example advises against including passwords or unnecessary sensitive personal information in requests.
- Review the page for accessibility, including meaningful heading structure, useful image alternative text, and accessible connected content, with WCAG 2.1 AA as a relevant benchmark where applicable.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Meet the Workplace Support team
This opening introduces the example team and signals that its scope and published guidance must be confirmed before employees rely on them.
-
This fictional Northstar team helps colleagues find the right workplace support across office and frontline locations. Use the People app for current team details and published ways of working; confirm the example scope before publication.
What this team handles
Clear boundaries help employees distinguish shared-workplace questions from requests that belong with another team or authoritative resource.
-
Illustrative Northstar example; confirm local scope before publishing. Shared workplace questions In this example, the team helps route questions about shared workspaces and workplace services. State the location and the workspace or service involved. Include what you need and when it is needed. For urgent safety concerns, follow your location’s established emergency and safety reporting process. What may belong elsewhere Some requests need a different team or app. Check current guidance in the People app before sending sensitive or specialist requests. For people-related support, use the People app to find the appropriate team or published route. For company-wide policies, consult Policy Hub. For open roles, use Job Board.
Prepare a useful request
These steps help employees provide location, need, timing, and relevant context while avoiding unnecessary sensitive information.
-
Follow the team’s current published process in the People app. These general tips are not a Northstar service commitment. Identify the location Name the site, office, or work area affected. Describe the need Say what is happening, what outcome you need, and when the work is needed. Add useful context Include relevant details and any steps already taken. Do not include passwords or unnecessary sensitive personal information. Use the published route Open the People app and follow the team’s current contact or collaboration guidance. If the route is unclear, ask your manager to help identify the appropriate team.
Find the team
The live directory gives employees a current way to identify team members when its source and audience access are configured correctly.
Upcoming team events
A connected calendar can surface relevant upcoming events without requiring the team to maintain a separate static list on the page.
Keep team details current
Ownership and correction guidance help prevent outdated scope or working instructions from sending employees down the wrong route.
-
Use the People app to find the team’s current information and published ways of working. Example setup note: confirm the owner and correction route before publication. Before contacting the team, check the People app for current team details and the appropriate route for your question. The page owner should correct outdated scope or guidance when the team’s responsibilities, audience, or working arrangements change.
How to use this template
- Replace the fictional Northstar introduction and examples with verified team responsibilities, audience, locations, and boundaries, and identify a page owner and correction route.
- Confirm the published contact or collaboration guidance in the People app or the organization’s current source, and link only to destinations that exist and are accessible to the intended audience.
- Configure the team_members block with the correct team or department directory source and check that office and frontline employees can view the intended records.
- Connect the calendar_events block to the appropriate event source, set the displayed event scope, and verify that the listed events are current and relevant.
- Publish the page in the appropriate team or department site, then ask a colleague unfamiliar with the team to locate its scope and explain how they would prepare a request.
- Review the page when team responsibilities, audience, working arrangements, directory membership, or event publishing changes, and correct outdated guidance.
Best practices
- State what the team handles and what belongs elsewhere using examples employees can recognize.
- Keep the request-preparation steps limited to details the team actually needs, and remind employees not to share passwords or unnecessary sensitive personal information.
- Preserve the direction to use established local emergency and safety reporting processes for urgent safety concerns.
- Verify the directory source and audience access before publishing instead of treating the live team_members block as authored sample content.
- Use the calendar_events source only for events intended for this page’s audience, and check that displayed items are current.
- Assign a named role as the page owner in your publishing process and define how employees can report inaccurate guidance.
- Link to authoritative policy and job destinations rather than copying their content into the team introduction.
- Check the page with keyboard navigation and accessible headings and image text, including against WCAG 2.1 AA where applicable.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What information does this Team Page template include?
It opens with a team introduction, then explains what the team handles and what belongs with other teams or resources. A request-preparation sequence helps employees describe location, need, timing, and relevant context. Live team-member and calendar sections can surface current directory details and upcoming events when correctly configured.
Is this template suitable for every team?
It is a starting point for teams that need to explain their remit and help employees find the right way to work with them. The example uses a fictional Workplace Support team and explicitly asks editors to confirm local scope before publishing. Replace that example with verified responsibilities, audiences, and routes; do not imply a service commitment that the team has not established.
Who should own and update the page?
Assign a page owner from the team or its communications support who can verify scope and published guidance. The example says to correct outdated information when responsibilities, audiences, or working arrangements change. Set a review cadence that fits the team’s change rate, and check the page after any relevant change rather than relying only on a calendar reminder.
How often should the team directory and events be reviewed?
The template does not prescribe a review interval. Check the directory source and event feed before launch, then verify them on the organization’s normal content-review cadence and whenever team membership or event publishing changes. Remove or correct stale details promptly so employees do not rely on outdated routes.
Does this page meet a regulatory or accessibility requirement by itself?
A page template does not establish legal compliance, and the example makes no regulatory claim. Review the published page against your organization’s accessibility requirements, including WCAG 2.1 AA where applicable, and make sure headings, image alternatives, and linked destinations are usable. Follow local requirements for workplace safety and sensitive information rather than treating this page as an emergency or policy procedure.
What is a common mistake when adapting the example?
A frequent pitfall is publishing the fictional team scope or leaving the directory and calendar connected to the wrong source. Another is directing urgent safety concerns to a general team route instead of the established local reporting process. Confirm each route, audience, and connection, and keep the warning about not sharing passwords or unnecessary personal information.
Can we customize the page for a department, project, or company team?
Yes. Adapt the site_type and page content to the audience, then keep the page focused on orientation: what the team owns, what it does not own, and how to find current details. Retain the request-preparation steps only if they fit the team’s actual process, and point employees to authoritative policy or service pages rather than copying those documents here.
How do the directory and calendar sections get their content?
The team_members section is live directory content and requires the correct team or department source; verify that intended office and frontline audiences can access it. The calendar_events section is also a connected block, so configure its supported event source and confirm that it contains the events meant for this audience. The other text and steps are authored page content, not automated workflows.
How does this page improve on an informal team description?
A description alone may name a team without explaining its boundaries or what employees should include when asking for help. This template pairs scope with a short request-preparation sequence and points readers to current team details and events. It also makes ownership and correction of outdated guidance part of the page’s upkeep.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Team Page ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.