Understanding Projects: Your client and campaign hubs

Projects are one of the most important features in Juma because they change how your team works with AI. Think of a Project as a collaborative space that holds all the context about a client, campaign, or task. They work like AI assistants where you set up the knowledge once, and then everyone on your team can reuse it.

Why Projects matter

Normally, every time someone on your team starts a new chat, they'd have to re-explain the brand voice, the target audience, and the strategy. That's exhausting and it leads to inconsistent work.

With Projects, you build the context once. You add the brand guidelines, the audience info, past examples, whatever the AI needs to know. Then everyone in your Juma workspace can create from that same foundation. No more re-explaining. No more inconsistent output.

How to organize your Projects

You can set up Projects per client, per campaign, per type of work, or per task. Basically, whatever makes sense for your team.

Many agencies create one Project per client and do all their work inside these Projects. This way, everyone working on that client account has access to the same context and can jump in without needing a handoff.

How to create a Project

To create a new Project, click the plus button in the sidebar or go to the Projects page and click New project.

You'll need to:

• Set up a name for your Project
• Pick an icon (optional)
• Add a project description (optional)
• Choose whether to use knowledge from existing Projects and build on top of it
• Choose a permission level (private, shared with everyone, or shared with specific people)

Once you create your Project, you'll set up the knowledge inside. This is where you add all the context your Project needs to know. We cover this in depth in the Project knowledge article, but basically, once you've set that up, all chats created inside this Project will automatically use that knowledge.

Project permissions

You can control who has access to each Project. To manage permissions, hover over any Project, click the three dots, and select Project settings.

You have three sharing options:

Share with everyone in the workspace: This makes the Project visible to your entire team. Anyone in your workspace can find it, open it, and collaborate inside.

Make it private: Only you can see the Project and the chats inside, unless you specifically invite people later or decide to share it with the whole team.

Share with specific people: You'll see a list of everyone in your workspace, and you can pick who gets access.

Understanding roles: Owner vs. collaborator

When you share a Project with specific people, you'll assign them a role:

Collaborator: Can work inside the Project and create chats, but cannot edit the Project itself, delete it, or invite other people.

Owner: Has full control. Can do everything a collaborator can do, plus edit Project knowledge, delete the Project, and invite other team members.

Once you've set your permissions, click Continue and you're done.

Sharing Project links

You can also share a Project by copying its link. Click the three dots next to your Project and select Copy link to project.

Keep in mind that link access depends on your Project's permissions:

• If the Project is private, no one else can open the link (even if you send it to them)
• If the Project is shared with everyone in the workspace, anyone on your team can open the link
• If the Project is shared with specific people, only those people (owners and collaborators) can open the link

Pinning Projects

Don't forget to pin your most important Projects so they're always accessible in the sidebar. This keeps your frequently used Projects easy to find.

Getting started with your first Project

Pick a client or campaign you know well. Create a new Project and add the basic context (we'll cover Project knowledge in detail in another article). Test it with something simple, like a blog intro or social post. If the output sounds right, you're set up correctly.

Once it's working, invite your team. They'll use the same context you built, no handoff needed.