Recommend awork (Referral program)

You like awork and you would like to recommend it? We would be very happy about that and therefore we would like to reward your efforts. 🎁

If you successfully recommend awork to others and a 12- or 24-month contract is booked, you will receive the monthly value of the new contract credited to your next invoice. And this for every single successful recommendation!

Sample calculation

You recommend awork and its being booked with a premium plan, annual billing cycle and 10 users. The monthly value is 10 users x 10 EUR = 100 EUR.

You will receive a 100 EUR credit on your next awork invoice. 🎉

The recommended team, also receives the same value as a discount on the first invoice.

The same applies if the team first books a monthly plan and later switches to a 12 or 24 month cycle.


To receive the discounts, the recommendation must be made via the automatic form under Settings -> Workspace -> Recommend awork.  


To get the discounts your workspace must be in a paid awork plan when you recommend and when the other team books awork.  

Unfortunately, the payout of credits can not be done. But if you want to earn money with the recommendation of awork, please have a look at our partner program.


What is a Workspace?

A workspace is a group of people working with awork to manage their work. Usually it will comprise of the people that work together with you at the same company.

If you register for awork, you will be asked to create a workspace within the registration process. All you need to do is to enter your colleague's email addresses and names.

Of course, you can be part of multiple workspaces with your awork account and switch workspaces within your user profile.

Tipp: If you book a premium subscription, it is tied to the workspace not to your personal account.

How can I invite team members?

You can invite your workspace during setup or at any point later on. Just go to "workspace" / "Users" and invite your workspace.

What can I change about my team?

To make awork your own you can change the name and the logo of your workspace within "Settings" / "workspace ". Furthermore you can set a custom URL if your team booked the enterprise plan.

You can also import data into your workspace here. 




Teams allow you to group projects and users in your workspace and limit their visibility to other teams.

This way it is possible that teams can only see their own projects, but not the projects of other teams.


Creating teams

In the menu item Settings -> Teams you can manage the teams in your workspace.

As long as you have not created any teams, you will not see an option in your workspace to assign users or projects to teams or to filter by them.

To create a new team, first click on the add team button. You have to give your team a name and choose a colour and an icon. The greyed out icons represent icons that you have already used for other teams. You can still use them for newly created teams.

Once you have created a new team you immediately will be directed to the user selection. Here you can staff your new team.


Assign users to teams

You can assign users to your teams in the team overview under Settings -> Teams. Each user can be in as many teams as you like at the same time.

Click the More button (with the 3 dots) of the respective team and then select Assign user. A window will open where you can select or deselect the users.

Users also have a team selection on their user detail page (directly below the name) where you can select the teams for the user. As these changes might impact the permissions of the user you need admin permissions to be able to make these changes.

When inviting new users you have to select a team to which the respective user will be assigned. You can change the team assignment after the invitation at any time in the settings or the user details.


Assign projects to teams

Projects have a team selection on the project details page and in the editing window, which can be used to determine the team member.

If there are sufficient authorisations for the project, the teams can be changed. However, only those projects that you can see yourself are available for selection here.

If you create a new project and are only allowed to see the projects of your own teams, you must assign the project to one of your own teams when you create it.


Limit visibility to own teams

In the settings of the authorisation roles (Settings -> Permission management -> Role details) there are two options: "Only projects from own team" and "Only users from own team". If these are activated, users of this authorisation role can only see the projects or users of their own teams, or the set authorisations then apply.

For example, if I activate "Only projects from own team" for an authorisation role and then only assign view permissions for the project details, tasks and times, then users can only see the projects of their own team and only with these view permissions. 

If the setting is not activated, the permissions set for project details, tasks and times apply to all projects in the workspace.


Which projects can I still see?

If a user is assigned to a project that does not belong to one of her teams, the user will still be able to see it. The permissions of the respective project role that the user has in this project apply.

If a user is the creator of the project, she may see and edit the project at any time.

If a user is only assigned to a task of a project that she is actually not allowed to see, she will be allowed to see the task only, but will not be able to see the project details.


Filter by teams

If teams are created in the workspace, there are filters that allow you to filter by team.

You can find these filters for instance here:

  • Team planning
  • Time reports
  • Task views
  • Project overview
  • User overview

Note that it makes a difference whether, for example, time reports are filtered by teams via users or projects.

If you filter the projects by teams, all time entries of the projects assigned to the team are shown. These can also be time entires of users who do not actually belong to the team.

If you filter the users by teams, all time entires of the users who belong to the team are shown. However, these do not have to be all time entires which have been tracked on the project.


Deleting teams

Teams can be deleted at any time in the team overview under Settings -> Teams via the menu of the multi-button.

The users will automatically be removed from the deleted team.

If projects were assigned to the team, they can be moved to another team by selecting this team within the deletion window.


Switch off teams

If you don't want to use the teams in your workspace anymore, you only have to remove all teams and the team filters and selections in your workspace will disappear.

Project Types

It is important to keep an overview over projects. Therefore you can classify them via project types and know directly what kind of project it is. Furthermore, all the information like status, role and task bundles are related to the project types. Creating a project you can easily import all this information by the choosing the type.

How can I create project types?

To create a project type, you to go to Settings / Project. Here you will find all your existing types and you can create new ones.

This will open a pop-up where you can name the type, write a short description and select a nice little icon. When you let the check mark in "Navigate to type" set, you will be forwarded to the type details, when you save it.

Within the details page you can add project status, task status and task bundles to your project type.



Creating a project status

When creating a project status you just need to put in a name and match it to a project phase. You can set the following project phases:

  • Planning
  • Progress
  • Canceled
  • Done

Keep in mind that task from projects in the phases planning, canceled and done will are not shown within My Tasks and the project will not be shown in the dashboard. 



Create task status

If you create a new task status you need to set the name and the type. You can also select a logo. This helps to differentiate the status, if you have more than one status with the same color.

The colors stand for the following task status types:

  • Blue (To-Do): Tasks you are not working on, e.g. backlog tasks
  • Yellow (In Progress): Tasks you are actively working on
  • Red (Stuck): Tasks you cannot work on because of an obstacle 
  • Purple (In Review): Tasks waiting for superior or client
  • Green (Done): Tasks you finished


Adding a task bundle

Just select the task bundle you want to add to your project and choose in which status it should be added. This comes in handy if you need certain bundles only at a later time in you project. You can, of course, add as many task bundles as you want to a project type. These will show up as lists in you project.


Add automations

You can also add automations to your project type. Just click the + symbol and select your trigger and action. You can find more information about automations here.

The automation will only be added to newly created projects. To add the automation to existing projects you need to go to the project settings.

You can add multiple automations to one project type.


Task Bundles

Task bundles help you to organize your projects even better. If you need a set a predefined tasks for your projects, you can just create a task bundle and later (automatically) add it to your projects as lists of tasks. This way you also have the option to create standard projects plans by connecting task bundles with a project type.

There are three ways to create task bundles in awork:

  1. Create a task bundles from scratch
  2. Import a bundle from our public library
  3. Create a bundle from an existing project

Create tasks bundles from scratch

Go to Settings -> Task Bundles. Now click "Add Task Bundle" and enter a name, add a description and assign a logo. 


Now you can add task lists and tasks, just as you do in a project.


By clicking the three dots next to the task you can edit the task details. You have the option to add the following:

Furthermore you can set the start date and the deadline for a task in reference to the time the task gets created (as in "added to a project"). When setting both start date and deadline the task will show up in the timeline of the project the task bundle is added to.


Import from our library

Go to Settings -> Task bundles. Now choose the option "Templates from awork". A windows with our task bundle library will open. You can click on the template to see the details and import them to your workspace via the small arrow.


The detail page describes the task bundle and gives you the option to read our blog article that describes the bundle. You can also see all lists and tasks in details and import the bundle into your workspace. 


Of course you can edit the task bundle (e.g. delete or add tasks) after the import to make it fit your process. 


Create task bundles from a project

A new task bundle can be created from the existing tasks and lists of a project.

To do so, go to the project tasks in the list view. You can save the whole project as a task bundle by clicking the More button. All task lists and tasks including their details are saved as a task bundle and can be reused in other projects.

Individual lists of a project can also be saved as a task bundle. To do so, click the More button at the respective task list and select the option to create a new task bundle.

Edit task bundles

You can edit task bundles at any time. Go to the overview via Settings -> Task bundles and click on the name of the bundle you want to edit. You now have all the options that where available when creating a task bundle. 

Additionally you can reorder task lists, delete the list or delete all tasks from a list 


Tipp: If you change a task bundle that is already used in projects or project types, it will have no effect on existing projects. The changes will only apply when this task bundle is newly added to a project.

Add tasks bundles to project types

To connect a task bundle with a project type, click on the three dots in the top right and select "Manage Project Types". Now you can either edit existing connections or create new ones via the "Add to project type" button. 

The next step gives you the option to select a project type and decide in which status the task bundle should be added. If you don't select the option "project creation" the task will appear when you switch the project to the selected status. 


Of course you can add task bundles to you project types from within the project types as well. We describe how to do it here.

Add task bundles to a project.

If you want to add the task bundle to a single project, and not the project type, just navigate to your project tasks and click on the “Import Task Bundle” Button. Select the bundle you want to add and you are done.

Of course you can import templates from our library here too.


Type of Work

The Type of Work describes the basic kind of work that you plan to track your times on (e.g. 'design', 'admin', 'sales') and are available in all reports. This helps you to get a good overview about how you spend your time.

How can I create new types?

To add a new Type of Work navigate to “Settings” / “Type of Work”. Here you can add a new type. You just need to put in a name and select a logo.


Where can I set the Type of Work

The type of Work is set within a task. The Type of work will now be preselected when tracking times on this task.


If you don’t track your time on a task you can set it when tracking your time.




Permissions help you to set who is allowed to read or manage the different parts (e.g. project details or project settings) within your awork workspace.

Permissions itself are based on global permission roles and project permission roles. The global permission role sets the users' permission for the whole workspace and across projects. The project permission role only applies to the project where the user is assigned to that role.

You can define what each role can do and see. The admin can always see and edit anything in your workspace. The permission management can only be changed by an admin.


Global Permission Roles

The global permission roles set your permission for the whole workspace and across projects.

To create a new role click on + Add Role. Now you can enter a name and decide if you want to configure the role on your own or use a preset provided by awork.

You can get more information about how to configure the roles here.

Of course you can edit or delete roles here and you can also reset a role to a preset at any time. If you click on the name you will get to role details. The admin and the guest role can't be edited or deleted. The admin has access to all parts of the workspace. You can find more information about the guest here.

Tip: If you want that a user only has access to certain projects take away his global permissions and just assign him/her to projects via a project role.


Project Persmission Roles

Project Roles set your permissions on project level. 

To create a new role, click the +Add Role button. Now you can set the name and decide if users with this role can see/edit project details, see/edit project tasks and see/edit project times.

If you click on an existing project role you get to the details.

One of the project roles can be defined as the default role. This role will then be preselected when staffing a project team. If the default role is deleted or the default is deactivated, another role must be selected to be marked as default.



Assigned Permissions

Here you see a list of all active users in your workspace. You can assign them their global permission role. A user can only have one role.

Tip: You can't move yourself out of the admin role because you would lose access to this page by this.



Permissions: Explanation of the settings

At the configuration of roles, we separate between permissions and menu item visibility. Permissions determine if you can access (manage or read) certain objects, e.g. project tasks. The menu item visibility determines if an item is shown in aworks main menu for a certain role. 

Tip: The permissions are also valid if you try to access awork via our API.




1. Can create new Projects


  • Users can create projects (no matter what permissions they have for Project Details)


  • Users can't create projects

The user that creates a project will always have all permissions for that project. This permission can't be revoked. 

2. Project Details




  • Users can't see or edit projects (except if they get permission via the project role)

3. Project Tasks


  • Users can create, edit, see and delete tasks in all projects
  • Users can import task bundles into projects


  • Users can see tasks in all projects, but can't create, edit or delete them
  • Task details can't be edited. I.e. users can't comment on tasks
  • Users can see the aggregated times for tasks and projects


  • Users can't see or edit project tasks (except if they get permission via the project role)
  • Users can create and edit private tasks
  • Users can't see the aggregated times for tasks and projects

4. Project Times


  • Users can track times for all projects
  • Users can see, edit or delete all the tracked times in every project


  • Users can track times for all projects
  • Users can see all the tracked times in every project


  • Users can't see tracked times (except if they get permission via the project role)



1. User Details


  • Users can see the user overview
  • Users can deactivate other users
  • Users can edit or delete other users
  • Users can see user details
  • Users can tag other users in the user details
  • Users can assign other users to projects
  • New users can only be created by admins -> Managing Permissions is not enough



  • Users can't see the user overview or details
  • Users can only assign or tag users in a project from the projects team 

2. User Times


  • Users can see, edit and delete the time tracking entries in the user details of other users


  • Users can see the time tracking entries in the user details of other users


  • Users can't see the time tracking entries from other users



1. Client Information


  • Users can see clients in the client overview
  • Users can see the client details
  • Users can create, edit or delete clients. 


  • Users can see clients in the client overview
  • Users can see the client details


  • Users can't see the client overview or details



1. Project Settings


  • Users can create new project types or edit/delete existing ones


2. Task Settings


  • Users can see, create, edit and delete task bundles in the settings


3. Time Tracking Settings


  • Users can see, create, edit and delete new type of works in the settings


4. Workspace Settings


  • Users can see the workspace settings
  • Users can change the name and the logo of the workspace
  • The workspace can only be deleted by admins. Managing Permissions is not enough


Menu Item Visibilty

On this page, you can decide which menu items are available to users in this role. Just click on the eye icon to activate/deactivate a menu item.


My Work

  • My Tasks
  • My Time Tracking


  • Projects
    • This setting is connected with Project Details. If users have no rights there, no projects will be shown in the project list.
  • Users
    • This setting is connected with User Details. If users have no rights there, they won't see Users either
  • Clients
    • This setting is connected with Client Information. If users have no rights there, they won't see clients either.
  • Task Views
  • Time Reports


  • Workspace
  • Project Types
    • This setting is connected with Project Settings. If users have no rights there, they won't see project types either.
  • Task Bundles
    • This setting is connected with Task settings. If users have no rights there, they won't see task bundles in the settings either.
  • Type of Work
  • Permissions
  • Integrations


Permissions: Presets

Presets are pre-defined Global Permission Roles that you can use in the permission management. The following presets are available:



Menu Item Visibility







You can automate processes in awork by setting tiggers and actions. You can set automations for a project type or single projects.

Set up automations

Select trigger

First you need to select a trigger which is the event that will start the automation. You can select triggers by category or just use the search to find all available triggers. 


For some triggers you need to set further conditions. Elements that need such conditions are marked. If you click on the marked element you can either select options or enter your input.


Tip: Triggers cannot be triggered by other automations. In this case nothing happens.

Triggers will be just triggered once per day in the morning. If you create new automations, that depend on a timeframe, they start triggering the next day.

Select action

Now you need to select your action(s). Again, you can select these by category or use the search to find all available actions. 


For some actions you also need to set further conditions. Elements that need such conditions are marked. If you click on the marked element you can either select options or enter your input.


You can set multiple actions for one automation. 

Automations in project types

To add automations to your project type, navigate to the type. Just click the + symbol and follow the steps above. 

You can add multiple automations to the same project type.


Transfer changes to projects

If changes are made to an automation in the project type, these changes can be transferred to all projects of the type. Only ongoing and planned projects are taken into account here. The changes are not transferred to completed projects.

After saving the change, a window appears in which this can be confirmed.

Note: If independent changes for automation have already been made in the project, these will be overwritten.

Automations for single projects

To create an automation directly in a project, navigate to the project settings and create the automation via the + symbol. Just follow the steps described above. 

The automation will only be added to this project and not to other projects of this type. 

You can add multiple automations to one project.