> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/system-administration/user-and-contact-administration/creating-assignable-users-and-organisations.md).

# Creating Assignable Users and Organisations

## Overview

This page explains how to create assignable users, such as contractors who can log in to view and edit tasks assigned to them, for example via the [mobile app](/security-and-support/faqs/troubleshooting/mobile-app.md).

This is useful for managing:

* External Agencies to assign [Request Tasks](broken://pages/wLFnJQEV40zX1rcGC6KR)
* Recovery Agencies to assign [Needs & Tasks](broken://pages/cbvxkWADYBnySUMuIgVf)
* Subcontractors for [Fire Prevention Notices](broken://pages/aVcVymyPFayQ3Z01C5aq) who can view [FPN Subcontractor Tasks](broken://pages/PZym7K6PlrQboZV0I0lo)

By restricting their access a sub-register, these users can view tasks assigned to them but not other secure information.

By delegating tasks and giving a level of task autonomy to external users and organisations, processes can be streamlined and made more efficient.

Once properly configured, users or organisations assigned tasks can receive automatic notifications on assignment.

## Creating Assignable Users

To create a user that can be assigned tasks:

1. Create a position (e.g. ABC Contracting) with relevant [security policies](/system-administration/configuring-the-system/positions.md#security-policies) (the easiest way to do this is to [copy an existing position](/system-administration/configuring-the-system/positions.md#copying) such as a contractor which has security policies pre-configured).
2. [Create a contact](/system-administration/user-and-contact-administration.md#creating-user-accounts), tick [user account](/system-administration/user-and-contact-administration.md#user-account) and [add the position](/system-administration/user-and-contact-administration.md#adding-and-removing-assigned-positions) (e.g. ABC Contracting) to it.
3. [Enable the position when configuring the Event register](/system-administration/managing-events.md#positions) (optional) if you want to allow them to access a specific register (such as FPN Subcontractor Tasks).
4. Test [going on duty to the Event](/concepts-and-fundamentals/on-a-computer/working-with-events.md) to begin working with it. You can temporarily set the user's email to your own to test assignment and notifications. Going on duty will enable assignment of tasks in the relevant Assignment field. You can also put users on duty using the [Bulk on Duty](/system-administration/user-and-contact-administration.md#bulk-actions) function.
5. Use the Welcome Email to send account details to the new user or organisation.

{% hint style="warning" %}
Important: There needs to be at least one user on duty in the position for it to become assignable. If no users are on duty, you can put them on duty using the [Bulk On Duty](/system-administration/user-and-contact-administration.md#bulk-actions) function.
{% endhint %}

## Creating Assignable Organisations

You can optionally set up an organisations to assign to an organisation instead of an individual. When doing so, an email account is still required for notifications and sign in. You can use a generic contact with a generic email address for this. You can also use a generic organisation such as 'Contractor'. This is the recommended way.

To create an organisation that can be assigned tasks:

1. Follow the [steps for creating assignable users](#creating-assignable-users)
2. Attach the position to an existing organisation using the [Organisation](/system-administration/configuring-the-system/positions.md#organisation) setting

{% hint style="info" %}
When a Contact is upgraded to a user it becomes possible to select an Organisation from the list to link the user to. This was a previous way to create assignable users. In the current version it is the Position rather than the Organisation determines assignability. You can still use this now as an optional reference link.
{% endhint %}

## Instructions for Users

Refer users to the Quick Start Guide to get them up and running once you have sent them their link to set a password. Their username will be the same as the email you set them up with.

{% content-ref url="/pages/gTGrSlSMwbJJAwO5KSkV" %}
[Quick Start Guide](/quick-start-guide.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cw.crisisworks.com/system-administration/user-and-contact-administration/creating-assignable-users-and-organisations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.