How access to other organisations works¶

These notes sit behind the tasks for sharing a release, giving a client access and delivering a release. Read them when you want the reason, not the steps.

Who at the other organisation can use it¶

Access is for the whole organisation: everyone there who can read shared work can open it, until it ends or you replace it. It is not limited to the team your client connected to you, and you cannot limit it to one team or one project there.

To give work to one person at your client, invite them to review. That is chosen from the team your client connected to you, and ends when they leave it.

The sender's record of who opened a release and what was taken shows each person at the other organisation by a code, not by name, unless that organisation chooses to show its people's names to senders on its Settings.

The end day¶

The day starts 90 days from today, and you can pick any day from today to a year ahead. Access ends at 11:59 pm of that day, India time (IST, UTC+5:30), and each grant has its own day. To move it, see Change, pause or end a client's access.

When access stops by itself¶

Every way of sharing stops while your organisation is suspended, while the project is in Recently deleted, and while the other organisation is suspended. That covers a client's access, a delivery, a delivery link and a review, and it resumes by itself when that is put right, with nothing ended or rewritten and no end day moved. The other organisation sees the same sentence it sees for any other pause; it is not told why.

Put it back¶

Resume this access on a paused row gives the release back exactly as it was, with the same permissions and the same end day. It does not extend or widen it.
A client paused in the project is listed under Clients paused in this project. Resume this client in the project puts back every access that was active before; one you ended stays ended, and one that ran out meanwhile stays ended.
A client paused in the project also cannot open a review you gave it or download a delivery you made to it, and you cannot invite it to review or extend its review until you resume the client. Resuming gives the review and the delivery back as they were.

Which acts are offered¶

Change end date is offered on an access that reads Active or Paused; the access keeps its release, its permissions and its state. An ended access cannot be put back: giving access again is a new grant.

While your organisation is suspended or frozen¶

End this access, End share and Turn downloads off work whatever your organisation's standing, even when it is closed. Pause this access, Pause this client in the project and moving the end day earlier also work while it is suspended or frozen. Moving the end day later, and anything else that gives, restores or widens access, waits until your organisation is in good standing again.

What your client did with it¶

Access record, in the access's menu, lists when people at the client opened the release and which files they downloaded, exported or copied. Each person shows as a code that stays the same for one person, unless their organisation has chosen to show its people's names to senders.

Map tools are worked out in the other organisation's own browser from the layers you send, so the tool list says what GISweaver offers them, not what they could work out themselves. What GISweaver enforces is which layers they get and whether they may download the release.

The download is the whole release as one archive with a manifest. Every file in it is handed over only once it has been checked. A file that does not pass is left out, and a WITHHELD.txt in the archive lists each one with the reason; the archive is refused only when none of its files may be handed over.

What the receiving organisation sees¶

A file reads Not included when the sender's access covers other files of the release, not this one. Access is for the receiving organisation as a whole: everyone who can open Deliveries can use what the sender allowed, and it cannot be narrowed to one team or one project of theirs.

A share stays the sender's and ends when they say. A delivery hands over files to keep and can be copied into the receiver's own projects; see Open a delivery you received.

Access roles and project responsibilities¶

Two different things are set on a project's Access tab. An access role (lead, contributor, viewer) decides who can open, edit or manage the project; you give it under Manage access roles. A project responsibility says who is answerable for the work, such as the survey lead, QA or client coordination; you set it with Assign responsibilities.

Assigning someone does not give them access, and giving someone a role does not make them responsible. Manage access roles is offered to the people who can manage roles on the project: owners, administrators, the branch's manager and the project's lead.