Canonical page: https://tellenze.com/guides/set-up-a-project Set up a Project # Give the work a home. Make the first step clear. Create a Project inside your existing workspace. Choose a lasting key, check who can use it and agree how work moves from a first idea to a checked result. [Follow the setup steps](#create-project)[Read Project Help](https://tellenze.com/help/projects-teams#set-up-a-project) - Project purpose - People with access - First useful task A shared place to begin Illustrative model · An illustrative setup path; the team chooses and saves each step. Before you create it ## Choose the place responsible for the result. A Project can hold work for a product, repository, service or initiative. A Team groups people and can own Projects as well as work of its own. Every work item belongs directly to one Project or one Team. Purpose ### Define the boundary. Write one sentence about what belongs here. Search Projects by name, key or description first, so a new Project has a clear reason to exist. People ### Know who needs access. List the people who will contribute and check results. If a Team owns the Project, its members can collaborate there. Work created in the Project still belongs to the Project. First result ### Choose a useful first task. Pick a small outcome you can define and review together. Use it to check the setup before filling the Project with a long list. An active workspace member can create a Project, within the workspace’s plan limits. This guide starts after workspace access is ready. Use [Set up your workspace](https://tellenze.com/guides/set-up-your-workspace) if you still need to prepare sign-in and membership. Create the Project ## A clear name. A key that lasts. Open Work → Projects → New project. Only Project name and Project key are needed. A key uses 2–8 letters or numbers, starts with a letter and becomes the permanent prefix for this Project’s work items. Choose a key you will still recognize later. You can change the Project name, but the key stays the same. Synthetic example · a Project setup Customer portal ### Help customers manage their receipts. NameCustomer portal KeyPORT · work identifiers use this prefix, such as PORT-1. BoundaryCustomer-facing receipt access and its supporting guidance. First taskCustomers can download a receipt for a completed order. - 01 ### Enter the name and key. Check the suggested Project key before saving. Choose a short, recognizable prefix rather than relying on the first suggestion. - 02 ### Open Project details. Add a Description explaining the purpose. Choose a portfolio group and Colour if helpful. Groups organize the directory; they do not change the Project’s behavior. - 03 ### Open Links & repository. Add a Website URL or Repository URL where useful. Check Default branch, which initially uses main. Saving repository details provides context; integration features may need a separate repository connection. - 04 ### Check Access. When private Projects are enabled, choose Workspace or Private and check the people with access. Otherwise the new Project is visible to every active workspace member. - 05 ### Choose Create project. Read any errors and correct the fields. After creation, open the Project and use Settings → Project to check its saved details. Check access with a teammate ## Let the right people reach the work. Ask a teammate to open the Project with their own account. Check its tasks and linked guidance too. A copied Project link does not grant access to the Project or to a private source outside it. Workspace visibility ### Every active member. Workspace Projects are visible to active workspace members. People with access can create work and edit an active Project’s details. Private visibility ### Check each access route. Private Projects restrict access through direct grants or membership of a Team that owns the Project. The creator and active administrators retain access. Removing one grant may leave another route. Settings permissions ### Use the right person. The Project creator and administrators manage Access and Workflow on active Projects when those features are enabled. Workspace administrators create and manage Teams. [Read Team ownership and access](https://tellenze.com/help/projects-teams#organize-a-team)[Understand access boundaries](https://tellenze.com/trust) Agree the working rules ## Make daily choices easy to understand. The new Project uses the workspace’s default workflow. Check the choices people will see before creating the first useful item. Settings and planning sections depend on permissions and enabled features. ### Check the workflow. Agree what each lane means and when a result needs review. Initial, Reopen and Completion settings control lifecycle behavior. A lane called Shipped is only a completion lane when configured that way. [Read workflow behavior](https://tellenze.com/help/workflows#understand-stages-and-lifecycle-behavior) ### Keep work types useful. Workspace administrators choose the available types. Settings → Work types can narrow that list for a Project. The Project cannot enable a type disabled by the workspace. [Read work-type settings](https://tellenze.com/help/projects-teams#choose-available-work-types) ### Prepare the guidance. Keep starting instructions in Documentation. Use a template where available to reuse a good task structure. If agents need mandatory reading, configure Required Context separately from ordinary document links. [Read Required Context Help](https://tellenze.com/help/required-context) To replace a workflow, open Settings → Workflow and review Stage mapping before Assign workflow. The mapping includes archived work. Check each old lane against its new destination before applying the change. Check the setup with real work ## One useful item. A place people can use. Choose New task in the Project. Add the outcome, context, acceptance criteria and assignees. Use the workspace’s current estimation scale and add a due date for a real deadline. Where project planning is enabled, Work shows execution, Backlog supports planning and Focus groups, and All work helps inspect the wider list. Start with the view that fits the next action. [Define the first useful work item](https://tellenze.com/guides/define-clear-work) Setup completion checks ## Ready for a shared start. - The purpose and key are clear.The team can explain what belongs here and recognize the identifier prefix. - A teammate can open the work.Check Project access and any source they need with their own account. - The workflow has a shared meaning.People know when to start, request review and use the configured completion stage. - The first task can be acted on.Its Definition explains the goal, the work and how the result will be checked. A few useful details ## Keep the Project setup clear. Do I need to be an administrator to create a Project? An active workspace member can create a Project, within current plan limits. On an active Project, people with access can edit its details. Access and Workflow management have additional creator or administrator permissions. Can I change the key later? The Project key is permanent and provides the work-item prefix. Check it before Create project. Use Settings → Project to update editable details such as the name, description and repository information. Does a Repository URL connect the provider? Repository details provide context. A separate connection and the relevant enabled feature may be needed for integration actions. Use [Connection setup](https://tellenze.com/guides/connect-your-tools) to check the supported path. Why is a setting or Project section missing? Check your permissions, Project archival, enabled features and the workspace’s effective plan. Some sections also need linked data or an integration. Ask the creator or an administrator to check the relevant setting; a copied URL does not add permission. Will archiving a Project free a plan slot? Plan limits count retained Projects, including archived Projects. Archiving keeps history and does not free that capacity. Ask an administrator to review the workspace’s effective plan if creation reaches its limit. Turn setup into useful work ## A clear place. A clear next action. Keep the first result small enough to define, finish and check together. [Define clear work](https://tellenze.com/guides/define-clear-work) Keep your next step clear ## Find the guide for your next step. [Browse all guides](https://tellenze.com/guides) COME TAKE A LOOK ## A little less busy. A lot more together. Curious? Join the waitlist and see how we welcome your team. Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace. [Join waitlist](https://tellenze.com/waitlist)Start with your email. No payment needed to join.