# User Records

Source: https://docs.astalty.com.au/guide/settings/users-settings/user-records

> Set up User Record Types to track staff documents, expiry, verification and rostering requirements.

User Records track staff documents, expiry dates, verification and rostering requirements. A User Record Type defines the rules that apply to one kind of record.

## How to Set Up and Manage User Records

Your organisation remains responsible for deciding which records and checks meet its obligations.

## Setting Up User Record Types

1. Open [**Settings > Users > Records**](https://app.astalty.com.au/settings/users/records).
2. Select **Create User Record Type**. If you are setting up records for the first time, you can [start from the suggested Record Types](#starting-from-the-suggested-record-types).
3. Enter a name, such as *First Aid Certificate*.
4. In **About this record**, explain what the Record is and where staff can obtain it. This optional content appears when staff add, edit or view the Record on web and mobile.

![The Create User Record Type drawer with the About this record field filled in for 100 Points of ID, describing the documents and point values needed](https://docs.astalty.com.au/assets/user-record-types-about-this-record-field.png)

5. Choose the options that apply:

   - **Document Expiry Date** records an expiry date.
   - **Record Requirement** makes the Record required for everyone.
   - **Document Upload Requirement** requires at least one document when the Record is created or updated.
   - **Upload Instructions** explains what to upload. It appears in the upload area while **Document Upload Requirement** is selected.
   - **Self-Service Uploads** lets Users upload their own documents. A visible but non-required Record Type appears as **Optional** in the app. See [Uploading User Records](https://docs.astalty.com.au/guide/scheduling/support-worker-app/uploading-user-records#record-status--notifications).
   - **Verification Requirement** requires another team member to verify a self-service upload.

![The Edit User Record Type drawer for First Aid Certificate, with Documents required ticked and formatted Upload instructions below it asking for a PDF or clear photo that shows your full name, the unit code HLTAID011, and the issue date and training organisation](https://docs.astalty.com.au/assets/user-record-types-upload-instructions-field-guide.png)

6. Select **Create**.

The **User Record Types** table shows whether each type is required, which [User Groups](#user-record-user-groups) need it, whether it expires, and whether it supports self-service or requires a document.

## Starting From the Suggested Record Types

Rather than typing out every Record Type by hand, you can add the ones most NDIS providers keep for their staff in a single step.

1. Go to [**Settings > Users > Records**](https://app.astalty.com.au/settings/users/records).
2. Select **Create User Record Type**.
3. On the **Want a head start?** card, select **Browse the library**.
4. In the **Suggested User Record Types** drawer, tick the Record Types you want, or use the checkbox in the header row to select them all.
5. Select the add button, which counts what you have ticked, for example **Add 6 Record Types**.

The card sits at the top of the create form, above a divider reading *or start from scratch below*, so building a Record Type by hand is still one screen away.

![The User Record Types card with an arrow pointing to the Create User Record Type button, above the record types list with Required, User Groups, Expires, Self Service, Documents Required and Required to Work columns](https://docs.astalty.com.au/assets/user-record-types-create-button.png)

![The Create User Record Type drawer with the Want a head start? card at the top and an arrow pointing to Browse the library, above the or start from scratch below divider and the Record Type Information fields](https://docs.astalty.com.au/assets/user-record-types-head-start-card.png)

### What You Can Add

The drawer lists ten Record Types, showing how each one will be configured before you add it:

| Record Type                 | Expires | Self Service | Verification |
| --------------------------- | ------- | ------------ | ------------ |
| Primary ID Document         | Yes     | Yes          | Yes          |
| Comprehensive Car Insurance | Yes     | Yes          | Yes          |
| Drivers License             | Yes     | Yes          | Yes          |
| First Aid Certificate       | Yes     | Yes          | Yes          |
| NDIS Worker Screening Check | Yes     | Yes          | Yes          |
| Police Check                | Yes     | Yes          | Yes          |
| Working with Children Check | Yes     | Yes          | Yes          |
| Support Worker Induction    | Yes     | No           | No           |
| Employment Contract         | No      | No           | No           |
| Position Description        | No      | No           | No           |

All ten are added as **required** Records, and all ten require at least one document to be uploaded. In the drawer, verification is shown as a shield icon beside the **Self Service** tick, with the tooltip *Verification required.*

![The Suggested User Record Types drawer listing ten record types with Required, Expires, Self Service and Documents Required ticks. First Aid Certificate, Police Check and Working with Children Check show Already added and have no checkbox.](https://docs.astalty.com.au/assets/user-record-types-suggested-drawer.png)

> **Adding all ten will flag missing records across your whole team**
>
> Every suggested Record Type is created as a **required record**, and seven of the ten also require verification. The moment you add them, every staff member who has not uploaded that document counts as missing it. This appears on each User's profile, in the [User Records Report](https://docs.astalty.com.au/guide/reports/user-records-report), and in any [User Record Notifications](https://docs.astalty.com.au/guide/notifications/user-record-notification) you have configured.
>
> On an established account, add only the Records you actually intend to collect. You can always come back and add more later, and each Record Type can be edited afterwards to make it optional or to require it of [specific User Groups](#user-record-user-groups) only.

> **Record Types you already have are skipped**
>
> A row greys out as **Already added** when a Record Type with the same name already exists, and it cannot be selected. The match is on the name only and ignores capitalisation. A Record Type you built yourself called "police check" therefore blocks the suggested **Police Check**, even if you set it up differently. If you want the suggested version instead, rename or delete yours first.

Added Record Types are ordinary Record Types from that point on. They are not linked to the library, so you can edit, rename, or delete them exactly like the ones you create by hand.

> **Who can add suggested Record Types**
>
> Only an Admin with the **Can manage User Records for all Users** permission can create User Record Types. It is **off by default** and the Account Owner always has it; see [Updating Roles and Permissions](https://docs.astalty.com.au/guide/roles-and-permissions#admin-permission-toggles) to switch it on.

There is a matching library for document templates. See the [Document Template Library](https://docs.astalty.com.au/guide/settings/document-template-library).

## Archiving a User Record Type

Archive a Record Type your organisation no longer uses instead of deleting it. An archived type stops being offered when staff create a new User Record and stops counting as a required Record, but Users who already have one keep it, and any configured [User Record Notifications](https://docs.astalty.com.au/guide/notifications/user-record-notification) stop sending for it. You can unarchive it at any time, which restores both.

1. Open [**Settings > Users > Records**](https://app.astalty.com.au/settings/users/records).
2. Open the actions menu for the Record Type and select **Archive**, then confirm.

> **Archiving switches off qualification requirements**
>
> If a [qualification requirement](https://docs.astalty.com.au/guide/settings/users-settings/qualifications) is built on the Record Type, archiving it stops that requirement applying. It drops out of roster checks, the schedule, worker suggestions and the Qualifications Compliance report, and Astalty does not warn you when you archive. Unarchiving the type turns the requirement back on.

Use the **Status** filter above the **User Record Types** table to show **Active**, **Archived**, or **All** types; it defaults to **Active**. An archived type shows a red **Archived** chip beside its name, and its actions menu offers **Unarchive** in place of **Archive**.

![The User Record Types list with the Status filter set to All and highlighted, showing an Archived chip beside the Disability Awareness Training record type](https://docs.astalty.com.au/assets/user-record-types-archived-status-filter.png)

### Archiving a Record Type That's Already in Use

A Record Type already used by a User Record cannot be deleted. Select **Delete** to see what's blocking it, then select **Archive instead** to archive the type without removing those Records.

> **A name already in use may belong to an archived type**
>
> Creating a Record Type with a name that matches an existing one, active or archived, is blocked with *A record type with this name already exists. If it is not in the list, it may be archived: set Status to Archived to find and unarchive it.* Switch the **Status** filter to **Archived** to find and reuse it instead of creating a duplicate.

## Using User Records

- Use the [User Records Report](https://docs.astalty.com.au/guide/reports/user-records-report) to find missing, expired and awaiting-verification Records.

![The User Records Report searched for Jack Brown, listing each Record's Status, such as Current, Awaiting verification, Expired or Missing, with its User, Record Type, Issue Date and Expiry Date.](https://docs.astalty.com.au/assets/user-record-reports-1.png)

- Configure [User Record Notifications](https://docs.astalty.com.au/guide/notifications/user-record-notification) to alert selected recipients when Records need attention.

- Make a Record Type mandatory for rostering to warn or block the scheduler when a worker's Record is missing or expired. See [Required Qualifications](https://docs.astalty.com.au/guide/settings/users-settings/qualifications).

- To manage a User's Records, open **Users**, select the User, then open **Records**.

![The Records panel on a User's profile, with Create Signature Request and Create User Record buttons and a list of Records, one Current and one Awaiting verification.](https://docs.astalty.com.au/assets/screen-shot-2024-02-20-at-7.59.40-pm.png)

## Send User Records for Signing

Create or open the User Record before sending its document for signature.

### Uploading a Record

1. Open [**Users**](https://app.astalty.com.au/users) and select the User.
2. Open **Records** and select **Create User Record**.

![A User's profile with Records selected in the side menu and an arrow pointing to the Create User Record button. A Missing Records panel above lists First Aid Certificate with an Add Record button.](https://docs.astalty.com.au/assets/create-user-record-1.png)

3. Select the **Record Type** and complete its required fields.
4. Upload files or choose existing documents from the User's profile.

If the Record Type has **About this record** set, it appears under the Record Type dropdown. The same box shows when editing or viewing an existing Record of that type.

![The Add User Record drawer for a First Aid Certificate, with the About this record box highlighted underneath the Record Type dropdown](https://docs.astalty.com.au/assets/create-user-record-about-this-record-alert.png)

If the Record Type has **Upload Instructions** set, they appear as a note inside the upload box. The same note shows when editing an existing Record of that type.

![The Add User Record drawer for a First Aid Certificate, with the About this record box under the Record Type and the formatted upload instructions showing inside the document upload box](https://docs.astalty.com.au/assets/create-user-record-upload-instructions-alert-guide.png)

If the Record requires a signature, you can choose to send it for eSigning immediately after creation, or select **No** to send it at a later time.

5. If the Record can be signed, choose whether to send it now.
6. Select **Create Record**.

![The Add User Record drawer with Employment Agreement as the Record Type, the Record Details and Documents sections highlighted with a PDF uploaded, signing set to Yes with No for sending immediately, and an arrow to Create Record.](https://docs.astalty.com.au/assets/user-records-2a-guide.png)

### File Types and Size Limits

As well as documents, you can attach **video** to a User Record. Astalty accepts **MP4**, **WebM** and **MOV** video files, alongside the usual PDF, Word, spreadsheet and image formats.

Every file on a Record, whether video or document, can be up to **500 MB**. A larger file is rejected with **File exceeds the 500MB size limit** and a format Astalty does not accept is rejected with **Invalid file type**, both before the Record is saved.

This is what makes a Record like **Support Worker Induction** practical to hold as a recording rather than a document. Once the Record is saved, select the video to play it in Astalty, the same way you'd open an attached PDF.

Only **PDF** and **Word (DOCX)** files can be signed, so a video never goes out in an eSignature request. If the only files you attach are videos, the **Does this User Record need to be signed?** question doesn't appear at all, and videos aren't offered when you send a Record for signing.

> **Support Workers can't upload video from the app**
>
> Video can only be attached from the browser version of Astalty. A Support Worker uploading their own Record through the mobile app can supply **PDF, JPG or PNG** files only, up to **15 MB**. See [Uploading User Records](https://docs.astalty.com.au/guide/scheduling/support-worker-app/uploading-user-records). If a Record needs a video, add it from the browser on the User's profile.

## Archiving or Deleting a User Record

Archive a User Record when it is no longer current but you need to keep its history. Open **Users**, select the User, open **Records**, select the Record, then select **Edit** followed by **Archive**. The Record stays in the list with an **Archived** status. Its active attachments are archived at the same time.

To restore it, open the archived Record and select **Edit** followed by **Unarchive**. Astalty also restores attachments that were archived with the Record. An attachment that had already been archived separately stays archived.

Deleting a User Record is permanent. Open the Record, select **Edit**, select **Delete**, then confirm. Astalty removes the Record and releases its attachments. A document stored only on that Record is deleted; a document that is also attached elsewhere stays with its other owner.

> **Pending signature requests block deletion**
>
> A User Record with a pending signature request cannot be deleted. The blocker lists each request. Open the request and resolve or cancel it, then try deleting the Record again.

### Changing a Fully Signed Record's Status

A Record's **Signature Status** is read-only while a signature request is in progress, and Astalty moves it to **Awaiting Signatures** when the request is finalised and to **Signed** once every signer has signed.

If only some signers sign through eSignatures and someone else signs on paper, a Record can show **Signed** while a signature is still outstanding. Once every eSignature signer has signed and no request on the Record is still in progress, **Signature Status** unlocks and offers **Awaiting Signatures** alongside **Signed**, so you can flag that a paper signature hasn't come in yet.

Choosing **Awaiting Signatures** shows a warning in place of the usual hint:

![The Edit User Record drawer's Signature section with Awaiting Signatures selected over a completed request, showing the warning 'Everyone on the signature request has signed, so this status won't update on its own. Set it back to Signed once the remaining signatures are in.'](https://docs.astalty.com.au/assets/user-record-signature-status-override-warning.png)

Set the status back to **Signed** once the paper signature is in. While the override stands, a repeated completion on the same request, or a change to another request on the Record, no longer flips the status back on its own - only setting it to **Signed** by hand clears it. The Record's details show a muted **Set manually** note under **Signature Status** as a reminder.

> **Deleting the request clears the override too**
>
> Deleting the Record's completed signature request returns **Signature Status** to **Not Sent**, the same as deleting any other request, and clears the override.

### When a Record Type Can't Be Sent for Signing

Not every Record Type can go out for signature. A Record Type can only be sent for signing when both of these are true on the Record Type in [**Settings > Users > Records**](https://app.astalty.com.au/settings/users/records):

- **Documents required** is ticked, and
- **This record is self service** is **not** ticked.

Self-service Record Types are the ones your staff upload themselves, such as a First Aid Certificate, so there is nothing for your organisation to send out for signature. Record Types that do not require documents have no document to sign.

When a Record Type doesn't meet both conditions, Astalty leaves the signing question out and tells you why, rather than offering a signing option that could never be completed.

**Creating a Record**: the **Does this User Record need to be signed?** question only appears for Record Types that can be signed. When you create a Record from a generated document, a short note under **Record Type** explains why the question is missing:

![The Create User Record from Generated Document drawer with First Aid Certificate selected and highlighted under Record Type, and a note reading 'First Aid Certificate is a self-service record type, so it isn't sent for signing.'](https://docs.astalty.com.au/assets/user-records-signing-unavailable-create-from-generated-document.png)

**Editing a Record**: **Signature Status** stays on **Not Required** and cannot be changed, with the same explanation beneath it:

![The Edit User Record drawer for a First Aid Certificate, with the Signature section highlighted, showing Signature Status fixed at Not Required and greyed out, and the note 'First Aid Certificate is a self-service record type, so it isn't sent for signing.'](https://docs.astalty.com.au/assets/user-records-signing-unavailable-signature-status-guide.png)

The **Send for Signing** button doesn't appear on these Records either, and they aren't offered when you send [multiple Records in one eSignature request](#sending-multiple-user-records-for-signing).

> **Clearing a Record stuck on Not Sent**
>
> **Documents required** and **This record is self service** can be changed on a Record Type that already has Records against it. If a Record was sitting on **Not Sent** when its Record Type changed, it can no longer be sent, but you can clear it. Open the Record and set **Signature Status** to **Not Required**, which is offered alongside **Not Sent** for this reason.
>
> Records already **Awaiting Signatures** or **Signed** keep the status they have, so a signature that is already underway isn't lost when the Record Type changes.

## Sending Multiple User Records for Signing

Send multiple User Records in one eSignature request when the same recipient needs to review and sign them together.

![The Create Signature Request for User Records drawer, with two Records ticked in the highlighted list under 2 records selected, and a Continue with 2 Records button at the bottom.](https://docs.astalty.com.au/assets/cleanshotuserrecordsmulti-guide.png)

### Uploading in the Support Worker App

Support Workers can upload their own Records in the mobile app. See [Uploading User Records](https://docs.astalty.com.au/guide/scheduling/support-worker-app/uploading-user-records).

## Verifying User Records

When a User submits a Record that requires verification:

1. Open the User's profile and select **Records**.
2. Open the submitted Record and review its documents.
3. Select **Verify** if the documents meet your requirements.

Astalty updates the Record's verification status.

![A User's Record opened from Records in the profile menu, showing its Record Details, a document under Documents and About this record, with an arrow pointing to the Verify button between Decline and Edit.](https://docs.astalty.com.au/assets/user-records-1.png)

### Notifications for User Records

User Record notifications can alert the Record Owner when a Record requires attention, such as when it is due to expire or needs an update.

![The Notification recipients section of a User Record notification, with The Record's owner ticked and highlighted above the User Groups and Users dropdowns.](https://docs.astalty.com.au/assets/user-records-2.png)

Managers, Team Members and Admins can also receive configured notifications and upload Records through the browser version of Astalty.

### Sending for Signature

1. Open the Record and select **Send for Signing**.

![A User Record with a Signature Status of Not Sent, and an arrow pointing to the highlighted Send for signing button beside Edit.](https://docs.astalty.com.au/assets/esign-user-record-1.png)

2. Complete the recipient fields and add a message when needed.
3. Select **Generate Request** to prepare the request in the connected eSignature service. See [Requesting Signatures](https://docs.astalty.com.au/guide/esignatures/requesting-signatures#finalise-a-signature-request).

![The Request Signatures drawer with the Signers section, holding a signer's Name and Email and an Add Signer button, and the Signature Request Details Title and Message highlighted, plus an arrow to Generate Request.](https://docs.astalty.com.au/assets/user-records-esignature-1.png)

![The Complete Signature Request window with a Signer selected, marked 1, and an arrow from the Signature field, marked 2, onto the document. A Send for signature button sits at the bottom.](https://docs.astalty.com.au/assets/esig-drag-fields.png)

## Video Walkthrough

Video walkthrough: user records.

## User Record User Groups

Rather than requiring a Record from everyone, you can require it only from the users in one or more [User Groups](https://docs.astalty.com.au/guide/settings/users-settings/user-groups). A Car Insurance Record, for example, only applies to the staff who drive.

When you create or edit a User Record Type you choose one of these, not both:

- **Required record**: everyone in your organisation needs the Record.
- **Required for some user groups**: only the users in the User Groups you select need it. Tick this option, then choose the groups under **Required for user groups**.

Ticking either option disables the other, so a Record Type is required for everyone or for specific User Groups, never a mix of the two.

The video walkthrough uses a Car Insurance Record Type to demonstrate a User Group requirement.

Video walkthrough: required records for user groups.

### Seeing Which User Groups Need Each Record

The **User Record Types** list has a **User Groups** column, so you can check who each Record is required for across the whole list instead of opening every Record Type one by one. The column shows one of three things:

- **The names of the linked User Groups**: only the users in those groups need the Record.
- **All Users**: the Record Type has **Required record** ticked, so everyone needs it.
- **-**: the Record Type is not required, so it is never reported as missing.

The **Required** column is ticked in both of the first two cases, so a Record required for a single User Group still counts as a required Record. The **User Groups** column shows how far that requirement reaches.

![The User Record Types list with a User Groups column. Car Insurance shows the VIC Team chip, First Aid Certificate and Induction Checklist show All Users, and Car Registration shows a dash.](https://docs.astalty.com.au/assets/user-record-types-user-groups-column-guide.png)
