PROJECT MANAGEMENT

One project.
Everything connected.

The people. The brief. The work. The next step.
Bring them together in a project your team and Xander can work from.

Start free

01 / LET’S BUILD A PROJECT

Stories from everywhere.
One shared home.

Imagine Atlas, a travel editorial told through wild landscapes, city stories, photography and words. Give it a project, then connect the people, knowledge and follow-ups that will get it delivered.

Native FridayHQ Atlas travel editorial project overview, with knowledge base and team access tabs, plus landscape and city films, countryside photography and editorial notes in Recent Content.
Atlas travel editorial · Example project overviewView full interface

A home for the work.

See the project’s recent content and open the piece you need, with its review status and workflow tags.

A place for the people.

Bring the project team together and manage the access each member needs.

Context that stays close.

Keep the brief, reference files and project knowledge alongside the work they guide.

02 / BRING IN THE TEAM

The right people.
The right access.

Emily coordinates. Maya edits. Alex reviews. Mason handles delivery. Bring them into the same project, with one place to see who has access and manage it as the team changes.

Native Team Access panel for the example campaign, showing Emily Davis, Maya Patel, Alex Morgan and Mason Reed, with Add Member, Edit and Remove controls.
Atlas travel editorial · Team AccessView full interface

Access that fits the job.

Set Create, Collaborate and Schedules permissions for each member on the project. In this example, Maya has Create and Collaborate enabled, while scheduling stays with the delivery team.

Admins can add members, edit their project permissions and remove access when it’s no longer needed.

Native Edit Permissions dialog for Maya Patel on Atlas travel editorial. Create and Collaborate are enabled; Schedules is off.
Maya Patel · Example project permissions

03 / GIVE THE PROJECT ITS CONTEXT

The brief belongs
with the work.

What’s the tone? Which deliverables are due? What needs checking before handoff? Keep those answers in the project’s knowledge base, as text notes and reference files.

Native project Knowledgebase containing a campaign brief, delivery checklist, internal production note and a brand guide PDF. Xander access is enabled for the brief, checklist and guide, and off for the internal note.
Atlas travel editorial · Knowledge baseView full interface

Keep the direction clear.

The editorial brief sets the tone. The delivery checklist keeps location captions and image credits visible.

Add the reference material.

Keep brand guides and supporting files with the project, with previews available from the knowledge base.

Choose what Xander can use.

Allow access entry by entry, or share all. Here, Xander can use the creative brief while the internal production note stays unshared.

04 / CONNECT THE FOLLOW-THROUGH

The task.
The actual work.

“Prepare editorial handoff” connects the Wild terrain film and City stories cut. Link both pieces to the task, assign the people involved and keep the handoff discussion with the next step.

Open the work from the task.

The editor and reviewer can get to the linked content without searching for the right file or conversation.

Follow it through the workflow.

Use project workflow tags to mark stages across content and tasks. Keep feedback, approval decisions and public sharing connected to the content.

Native Prepare editorial handoff task with Linked Content selected, connecting the Atlas Wild terrain film and City stories cut to the same task.
Prepare editorial handoff · Two linked content pieces
Example native Xander chat where Emily asks for a location-caption task for Maya and an image-credit message to Mason. Xander confirms the task and message.
Xander chat · Example editorial follow-up

05 / PUT THE CONTEXT TO WORK

Bring in Xander.
Move it forward.

Ask Xander about the project, review a cut in its content Discussion, or use Xander chat to turn a follow-up into a task. The project’s shared knowledge gives it context to work with.

Ask about what’s missing.

Use the project’s shared guidelines and review discussion to work through what still needs attention before handoff.

Give the next step an owner.

Ask Xander to create Maya’s caption-check task, set the deadline and send Mason a message about the image credits.

See what Xander can do

FROM THE BRIEF TO THE HANDOFF

Give your next project
a place to come together.