Skip to content

Commit a5bff8b

Browse files
committed
Add notes on unmaintained group accounts
1 parent c501121 commit a5bff8b

File tree

2 files changed

+50
-9
lines changed

2 files changed

+50
-9
lines changed

content/reference/common-requests.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,9 @@ unsure how to reach the site's owners.
5353

5454
## Gain access to an existing group account
5555

56+
[Read more about group admins and unmaintained
57+
accounts]({{< relref "group-accounts/administrators" >}})
58+
5659
As a prospective admin seeking access to manage a group account, you
5760
should first contact its existing admins and request access from them.
5861
See the answer above for how to identify the short name of the account.
@@ -66,9 +69,7 @@ transfer ownership as needed.
6669

6770
Group accounts are considered *unmaintained* if they have no active
6871
admins remaining. Accounts in this state will display an *Unmaintained
69-
group website* page if you visit their SRCF-hosted website. You'll need
70-
to contact the sysadmins in the first instance to recover such an
71-
account.
72+
group website* page if you visit their SRCF-hosted website.
7273

7374
## Grant group admin access to someone else
7475

content/reference/group-accounts/administrators.md

Lines changed: 46 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,54 @@ Each group account has a list of *admins*: SRCF users who manage the
99
account and its services. This includes access to the account in the
1010
control panel, permissions to edit files inside
1111
`/societies/<groupname>`, and receiving administrative email sent to
12-
`<groupname>[email protected]`. This list may also be used by an
13-
account's website to limit page access to current admins.
12+
`<groupname>[email protected]`. It may also be used by an account's
13+
website to limit page access to current admins.
14+
15+
This list is the canonical definition of who is responsible for a group
16+
account, and is independent of any committees or roles in a University
17+
club or society that a group account on the SRCF may happen to
18+
represent.
19+
20+
## Handover
1421

1522
We recommend that you keep your own handover documentation, covering
1623
what services and software a group account is using.
1724

25+
It is the responsibility of SRCF group account admins to keep their list
26+
of admins up-to-date, meaning both the appointment of their successors,
27+
and the removal of predecessors that should no longer have access.
28+
29+
SRCF system administrators will not process requests from users wishing
30+
to gain access to a group account, instead directing them to the
31+
account's current admins to make their request.
32+
33+
## Unmaintained group accounts
34+
35+
In order to maintain continuity of group accounts, we recommend keeping
36+
at least two admins at all times.
37+
1838
When a group account admin leaves the University without taking steps to
19-
retain access to their SRCF account, they may be dropped from the list
20-
of admins. A group with no admins is considered *unmaintained*, at which
21-
point some services will be suspended. To maintain continuity of group
22-
accounts, we recommend keeping at least two admins at all times.
39+
retain access to their SRCF account (which includes emails to their
40+
membership address bouncing, or otherwise not responding to emails from
41+
the system administrators), they may be dropped from the list of
42+
admins, and their account suspended.[^1]
43+
44+
A group with no admins is considered *unmaintained*, at which point some
45+
services (such as website hosting) will be suspended. If the group
46+
account is configured with a role email address, it may be contacted as
47+
a last resort, to inform the recipients of the situation and for them to
48+
nominate a stand-in admin and reactivate the site.
49+
50+
The SRCF has the responsibility as a data processor to prevent
51+
unauthorised access to personal data. If we're unable to verify the
52+
handover of an unmaintained group account (for example, if a group
53+
account has no contactable admins and no role email to fall back to), we
54+
will not be able to provide access to its contents. As a user seeking
55+
access to such an account, generally this means you will have to
56+
register a new group account and start from scratch.
57+
58+
[^1]: If your account has been suspended for being uncontactable, you
59+
can reactivate it from the [Control Panel](https://control.srcf.net).
60+
Note that you won't automatically regain access to your group accounts
61+
-- please [contact the sysadmins](https://www.srcf.net/contact) to
62+
request these.

0 commit comments

Comments
 (0)