Revoking access¶
Access is checked on every request, so each of these takes effect on the recipient's next page view or download.
| To stop | Do | Where |
|---|---|---|
| A whole share | Revoke it | The share's Revoke operation, drush file-share:revoke --share=ID, or the file_share_revoke tool |
| One recipient on one share | Remove them | The share's Recipients tab, or file_share_revoke with share and recipient |
| One recipient everywhere | Remove them from every share and end their sign-ins | drush file-share:revoke --recipient=ADDRESS, or file_share_revoke with recipient as an administrator |
| Everything one person shared | Revoke every share they issued | drush file-share:revoke --issuer=NAME, or file_share_revoke with issuer |
Invitees go too¶
Removing a recipient also removes everyone they invited, and everyone those people invited.
Automatic revocation¶
- Blocking or deleting an account revokes every share it issued. It also removes the account, and its email address, from every share it was given.
- Deleting a file or media item drops it from every share. The shares and their activity stay.
- An issuer losing access to a file, for example through a changed role, stops recipients downloading it. They get it back if the issuer does.
Domain patterns¶
A domain pattern stays in force until the pattern itself is removed. Removing jane@example.org from a share does not shut her out while *@example.org admits her. To shut out one person at a domain, remove the pattern and add the others by address.
A blocked account is the exception: its address must log in, and a blocked account cannot.