What a client may do¶
You choose these when you give a client organisation access. To see them from the client's side, read Open something shared with you.
Permissions¶
| Permission | What it allows |
|---|---|
| View the map | Look at the release on a map. |
| Comment | Start conversations about the release and answer them. They appear in your project's conversation (the map's Conversation panel), marked as from the client, under a band saying the client reads every answer in it. Your client reads only the conversations it started, with your answers in them. |
| Download original files | Download the map files of the release as you uploaded them. |
| Download map layers | Download what GISweaver made from the release, such as its map layers, in one archive, or one at a time. The original files are not in it. |
| Open project files | Download the files you kept with the project and marked Send with the release, such as PDFs and photos. Any other original needs Download original files. |
| Copy files into their own project | Copy the release's original files into one of their own projects in Draft or Review, where each is checked and filed as an upload is. |
- Each permission opens only its own door: Open project files does not download a map file, and Download original files does not open a file you kept with the project.
- Your own conversations stay internal; the client does not read them.
- When you pick Only the map layers I choose, Download map layers is switched off and unticked, because a derived product is not split by layer.
- Once your client downloads, exports or copies a file, that copy is theirs: nothing on GISweaver can recall a file that has left.
- If you pause or end the access while a copy is still running, the rest are not copied.
- A file crosses to another organisation only once it has been checked, whatever you tick; a file that is flagged, cannot be checked or is still being checked is left out.
Which files¶
- Every file in this release is the usual choice: the access covers whatever the release holds.
- Only the files I choose lets you search by name or kind and tick files. Your client still sees every file listed; the others read Not included and cannot be taken.
- Only the map layers I choose narrows what is drawn on the map; the file list stays as it is.
A grant narrows files, or map layers, or nothing: never two at once. A file the access does not cover reads Not included on your client's list. A file can be visible without being downloadable; see Download original files when allowed.
What each act does¶
You do these from the access's menu: see Change, pause or end a client's access.
| Act | What it does |
|---|---|
| Change which files | Untick the files they should lose. |
| Change end date | Pick a later or earlier day. |
| Turn downloads off | They keep the map and lose every way of downloading files from it. |
| Pause this access | They stop being able to open this release. Everything is kept, so you can put it back. |
| Pause this client in the project | They stop being able to open anything in this project, including access you give them while the pause lasts. |
| End this access | They lose this release for good. |