When you are assigned a task in LAFT, you will receive an email notification ( regardless of whether you are created as method 1 or 2) . The auto-generated email will look like this:

Here you will find all the information you need; task text, deadline, which building it applies to, etc. If it is a task with a deadline, you will receive a new notification when the deadline approaches if you have not completed it.

To process this, click on the “Go to work order” button. This will take you to LAFT in “protected mode”, and you will only work on the task you have been assigned. Here you can see the task text, deadline, add your own comments/attachments, view and fill out any checklists, and set it to the status Completed when you are finished. To change the status, click on the Start work button. The status will then first change to In progress. Then click again to set it to Completed.

Guide: How to fill out a checklist

Were there any discrepancies in the checklist? See tutorial: Creating work orders from checklists

Log in to LAFT with your username and password by going to https://id.laft.io

Regardless of whether you have been created as a supplier via method 1 or 2 above, your email address will be linked to a role in LAFT called “ad-hoc”. You will be able to use LAFT on the web with this role, and have access to the MittBygg module, as well as the document archive.

If you were created via method 1 , you should have received an email asking you to create your own password. If you did not receive this, you can click the Forgotten password button when logging in.

If you were created via method 2 , you have not been given a password, but you can still click the Forgot password button, enter your email, and create a password.

When you are assigned tasks, you will be able to process them in the MittBygg module.

Once you are logged in, you can choose to enter the MittBygg module to view your cases, or go straight to the Document Archive to upload files:

Here you will see an overview of your assigned cases, and can proceed to process them.

Other useful guides :
MyBuild on the web
How to use the document archive
How to fill out a checklist
Were there any discrepancies in the checklist? See tutorial: Creating work orders from checklists

Regardless of whether you have been created as a supplier via method 1 or 2 above, your email address will be associated with a role in LAFT called “ad-hoc”. You will be able to use the MittBygg section of the LAFT app with this role.

If you were created via method 1 , you should have received an email asking you to create your own password. If you did not receive this, you can click the Forgotten Password button when logging in after you have downloaded the app.

If you were created via method 2 , you have not been given a password, but you can still click the Forgot password button, enter your email, and create a password.

When you are assigned tasks, you will be able to process them right in the app:

Scroll to the right in the table to go to treatment:

You can add your own comments and photos, as well as complete/change the status of the case:

If a checklist has been attached, it will be here for completion:

You can also upload documents to the document archive of the object (building) the case is created on, navigate back to your cases, and view your previously completed checklists by clicking on the icon in the top right, here:

For using the app, see also guides:

MyBuild on app
Filling out a checklist
Were there any discrepancies in the checklist? How to create work orders from checklists

There are two ways you can use the document archive as a supplier:

• Via external upload (no user access to LAFT required):
  The municipality/organization that uses LAFT can open up for external upload. You will then be given temporary access to upload files to the desired folder, directly via email. This means that no username and/or password is required.
  How it works: External upload can be used when the LAFT user wants you, as a supplier (external) who does not have any user/access to the system, to upload documentation to the document archive.

The following is included in the email you as a supplier receive:

"Reply to this email (retain the original subject line) and attach documents to upload to the document archive. NOTE: Images must be added as attachments, not as part of the email itself."

When you view the reply to the email with the attachment(s), the attachment will be uploaded to the selected folder. The sender can also enter a personal message that will be included in the email, if they think you need more context.

When a file is uploaded, the file is located in the folder with an X in the "Approved" column on the right in the list. This is to indicate that this is an external file that has not yet been reviewed. LAFT users can right-click on the file and click "Approve" and the symbol will change to a check mark, indicating that someone has viewed and approved the document.

You will be able to continue uploading documents until your remote upload access is removed.

See also guidance: How to use the document archive

• Via LAFT on app or web :
  If you are registered as a supplier either via method 1 or 2, you have access to LAFT by logging in.
  • If you are created via method 1, the LAFT user will be able to control which buildings your user has access to, and you will therefore have access to LAFT (and thus the document archive) until your user is deactivated. When you are logged in to LAFT, either via LAFT or WEB, you will also be able to upload documents directly to the document archive.
    Web : To upload files, right-click on the desired folder.

App : Press and hold the folder you want to upload files to for about one second.

• If you are created via method 2, you will only have access to buildings in LAFT that you have an open task on. So to have access to the document archive, you must have an ongoing case. When you close the case (set it to Done), the building access will automatically be removed. Beyond that, you upload files in the same way as described for method 1.