While this is not a legal document and these principles are non-binding, failure to adhere to these principles may result in a ban from future CLASS events, at the discretion of the Board of Trustees (BOT).
Roles and Responsibilities
The owner is the sole individual in charge of the CLASS FetLife profile and website and is also listed as the owner of the CLASS Ireland FetLife group.
Responsibilities of the owner include:
- Posting content to the CLASS profile and website, including obtaining required permissions as outlined in the Photography and Writing sections below, and managing relationships as outlined in the relationship section below.
- Maintaining database of posted content and individuals with rights to request removal of each post.
- Maintaining a list of individuals on the Board of Trustees (BOT), as well as individuals currently serving as organisers, moderators, custodians, and the bursar. The owner is responsible for disseminating this information as necessary.
- Posting of CLASS events organised by approved organisers.
- Managing communication through the CLASS profile and email address, including directing potential participants to the applicable event organiser or munch moderator.
- Maintaining list of individuals banned by the BOT.
- Disseminating the list of banned individuals banned by the BOT to all CLASS organisers.
- Naming one or more backup owner(s) and providing access to the named individual(s), particularly in advance of prolonged periods of absence/inactivity.
- Providing backup owner(s) and successor with access to lists and databases listed above.
- Serving on the BOT.
- Selection of moderators for the CLASS Ireland FetLife group.
- Management of BOT, organisers, custodians, and munch moderators, as well as oversight of the bursar. The owner is also responsible for maintaining lists of individuals in each of these roles, and for directing enquiries to the appropriate individuals as required.
- Maintenance of the CLASS website.
- Approval of event budgeting, along with the organiser and bursar.
The owner is appointed for a term of up to one year. This term may be extended by unanimous vote of the BOT after each year of service for a period of up to an additional year. Owners may serve multiple terms.
The owner must nominate a successor from the BOT not less than one month prior to the end of their term. At the conclusion of the term, the former owner may remain on the BOT or step down at their discretion. This decision is to be communicated in writing to the new owner.
Board of Trustees
The board of trustees (BOT) serves as the voluntary governing body of CLASS.
Responsibilities of the BOT include:
- Approval of CLASS organisers by unanimous vote of current trustees.
- Decisions to ban participants, preferably by consensus though a majority vote of current trustees may be used if necessary.
- Review of any recorded incidents at CLASS events, including communication of lessons learned/best practices to the organisers and the group at large as deemed prudent.
- Approval of changes to these guidelines by majority vote of current trustees.
- Note: The owner may make emergency changes to these guidelines as needed. In the event emergency changes are made, it is the responsibility of the owner to notify the trustees and to seek a formal approval and/or additional revision of the guidelines in a timely manner.
- Trustees may also be asked to serve as moderators for the CLASS Ireland FetLife group and/or administrators for the website.
- Trustees meet minimally once per year to discuss current issues, appointment of new trustees, and ownership transition.
Appointment of trustees
- CLASS will attempt to maintain 5-10 trustees at all times.
- CLASS will make efforts to include in the trustees at least one top, one bottom, one woman, one man, and one trans individual.
- CLASS will aim to appoint a new trustee minimally every six months.
- Approval of new trustees is by unanimous vote of current trustees.
- Trustees may resign at any time via written message to CLASS. Once a trustee resigns, that individual must wait a minimum of six months before applying to re-join the board.
- In the event that trustees are unable to actively participate in discussions and voting, trustees may name a proxy for voting purposes in advance. Proxies are designated by written message to the owner, and may be designated for periods not exceeding two months.
- Trustees are considered inactive if three consecutive requests for a vote go unanswered for one week or longer, unless a proxy has been nominated in advance.
- Inactive trustees are not counted for voting purposes; the vote of an inactive trustee is not required for a majority or unanimous ruling. Inactive trustees may become active again by message to the owner within six months. Trustees inactive for six months or longer will be removed from the BOT and considered to be trustees emeriti.
- Trustees have one week to respond to all requests for a vote- either personally or by proxy. Trustees who have not yet voted must be contacted a minimum of three times within five days of the initial request for the vote, using a minimum of two communication channels, if the trustee’s vote is required to reach either majority or unanimity as required by the matter at hand. If no response has been received after one week, the trustee is considered inactive for the purpose of the vote in question; the vote of an inactive trustee is not required for a majority or unanimous ruling.
- A trustee (including the owner) may be removed by majority vote of remaining trustees. Any trustee may initiate this voting process.
Organisers are individuals who coordinate CLASS events. Organisers must be approved by a unanimous vote of the BOT. Appointment to the BOT also qualifies an individual as an organiser. Once approved, an organiser may be removed by a majority vote of the BOT.
Responsibilities* of organisers, for the events they are organising, include:
- Selection and booking of venue.
- Selection of participants.
- Approval of event budgeting, along with the bursar and owner.
- Providing owner with text and other required details for event posting.
- Making every effort to ensure individuals banned by the BOT do not attend events.
- Note: in addition to individuals banned by the BOT, organisers may refuse admission to any additional individuals at their discretion. The owner should be informed of anyone refused admission to the event if the organiser wishes for the BOT to consider banning the individual from all CLASS events.
- Establishing and communicating safety protocols for the event, including the use of safewords, monitoring staff, first aiders, and emergency procedures.
- Communicating the CLASS Code of Conduct to all participants, as well as any additional policies and procedures in place for the event.
- Establishing event photography policy in alignment with the photography selection below and communicating this policy to all participants.
- Selection and training of monitoring staff for events.
- Delegation of responsibilities to other participants may be performed at the discretion of the organiser. However, organiser is responsible for ensuring designees perform delegated responsibilities effectively.
*Note: CLASS events may vary widely in size and nature, consisting of anything from a small group in a private home to a larger group events in public venues, to virtual detention events and similar. Therefore, certain responsibilities listed above may or may not apply to specific events.
Note: Organisers are only required to serve the role of organiser at events for which they are listed as the official organiser. Additional organisers in attendance *may* assist the official organiser on a voluntary basis as agreed with the official organiser, but this is not to be expected or required.
Munch moderators are individuals who coordinate CLASS events. Moderators must be approved by a unanimous vote of the BOT. Appointment to the BOT or as an organiser also qualifies an individual as munch moderator. Once approved, an munch moderator may be removed by a majority vote of the BOT.
Responsibilities of munch moderators, for the munches they are moderate, include:
- Securing venue for the munch and pre-meet, including making bookings as appropriate.
- Selection of participants. Generally, any individual in good standing who has previously attended a munch is free to attend. New participants are typically asked to attend a pre-meet for vetting purposes prior to attending their first CLASS munch. However, each munch moderator may adjust these general policies at their discretion for munches they organise.
- Informing participants of venue for munch and/or pre-meet as appropriate.
- Providing owner with text and other required details for the munch event posting.
- Making every effort to ensure individuals banned by the BOT do not attend munches.
- Note: in addition to individuals banned by the BOT, munch moderators may refuse admission to any additional at their discretion. The owner should be informed of anyone refused admission to the munch if the moderator(s) wish for the BOT to consider banning the individual from all CLASS events.
- Communicating and enforcing code of conduct for the munch.
- Selection and training of assistant moderators for the munch. Assistant moderators do not require approval of the BOT, but may only assist the primary moderator in enforcing the code of conduct or in other administrative duties at the discretion of the primary moderator. Assistant moderators may not organise CLASS munches independently; any assistant moderator wishing to do so should contact the owner and express a desire to be approved as a primary moderator.
- Reporting to the owner any conduct at the munch which may indicate an individual is not suitable for participation in CLASS events.
Note: Munch moderators are only required to serve the role of moderator at events for which they are the official moderator or assistant moderator. Additional moderators in attendance *may* assist the official moderator on a voluntary basis, but this is not to be expected or required.
Hosts are CLASS-affiliated individuals providing or organising the hiring of a venue for CLASS events. The host and organiser of an event may be a single individual. Otherwise, the host is approved by the event organiser.
Monitors are CLASS-affiliated individuals appointed by an event organiser to help ensure events run smoothly. The duties of monitors vary by event and will be specified by the event organiser. In general, montiors may be asked to:
- Assist with timekeeping and logistics
- Listen for safewords and help ensure they are heard and respected
- Remind event participants of event and venue rules
- Provide aftercare and/or direct participants seeking aftercare to the organiser
- Contact the organiser with any questions on procedures, or if situations arise which the monitor is uncomfortable or unsure of how to handle.
Custodians are appointed by the owner to document and manage CLASS group supplies and equipment. If a custodian is not a member of the BOT, the appointment must be approved by majority vote of the BOT. Once approved, a custodian may be removed by a majority vote of the BOT, after which the owner must designate a temporary custodian to serve in this role until a new custodian is identified.
Responsibilities of the custodians include:
- Maintenance of the CLASS equipment and supply inventory, including items owned by CLASS and items on loan to the group.
- Requesting approval of the bursar and owner for any reimbursements for CLASS equipment and supply expenses.
- Facilitating transportation of CLASS supplies and equipment, including negotiation of loan of items between regions as required.
A bursar is appointed by the owner to document and manage CLASS group financial matters. If the bursar is not a member of the BOT, the appointment must be approved by majority vote of the BOT. Once approved, the bursar may be removed by a majority vote of the BOT, after which the owner must designate a temporary bursar to serve in this role until a new bursar is identified.
Responsibilities of the bursar include:
- Maintenance of the CLASS ledger.
- Record keeping for any financial matters for the CLASS group.
- Approval of event budgeting, along with the organiser and owner.
- Approval of any reimbursements for CLASS expenses.
Participants are individuals who physically attend CLASS events. Participants are selected and approved at the discretion of the organiser for each individual event. Participants are advised that each organiser and event may have different criteria for selection and approval of participants.
Friends are individuals listed as friends on the CLASS Ireland profile. Friends are accepted and rejected at the discretion of the owner. Potential friends are advised that a brief, polite note of introduction stating their reasons for interest in the group will greatly increase the chance of friend requests being accepted. Note that acceptance of a friend request does not have any bearing on selection for participation in events.
Only individuals who participate in CLASS events will be listed as teachers/students on the CLASS profile. Written permission will be sought from each individual prior to adding the relationship.
However, any friend of the CLASS profile is permitted to add relationship(s) to their own profile at their discretion. Not that relationship status does not have any bearing on selection for participation in events.
Group members are individuals listed as members of the CLASS Ireland FetLife group. Group members may be banned at the discretion of the group leaders. Group leaders are selected from the trustees and organisers at the discretion of the group owner. Note that group membership is not generally required for participation in events.
The owner is responsible for maintaining the CLASS profile and website, and may reject or remove any content at any time, with or without warning. However, friends and participants are welcome and encouraged to submit material for posting. Submissions are subject to the FetLife content guidelines. In addition, the following guidelines shall be followed when posting submitted material.
Photography is only permitted at CLASS events with prior permission from the organiser, host, and all participants in the photograph (including those in the background). The organiser may also designate a house photographer(s) responsible for all photography, including obtaining prior permission from all applicable individuals and ensuring the photographs are taken in a suitable location.
Photographs from CLASS events may be submitted for posting to the CLASS profile and/or website. To submit a photograph, send the file to CLASS (PM for email address). The following information must be included with each submission:
- Explicit, written permission from the submitter to post the photograph on the CLASS profile and/or website.
- Desired caption
- FetLife usernames for:
- All participants visible in the photograph (including those partially visible and those in the background
- Event organiser
- Event host
- Any others with a creative interest in the photograph as applicable (i.e., costumes, lighting).
If any of these individuals does not have a FetLife username, alternate contact information should be provided. Written permission (via email or PM) will be obtained by CLASS from each of these individuals prior to posting the photograph. Additionally, any of these individuals may request for the photograph to be removed at any time. CLASS will attempt to honour all requests for removal as soon as possible, typically within 24 hours
All accepted photographs will be uploaded as visible to all FetLifers and publicly posted to the website as applicable. CLASS will not transmit photographs to a third party at any point in this process. However, those submitting and giving authorisation for the posting of photographs are reminded that, once posted, CLASS is not able to guarantee that the photograph will not be disseminated by third parties viewing the photograph from the CLASS profile and/or website.
Posting of video content will be managed under the same principles as photography.
Participants and friends are welcome and encouraged to submit original written work for posting to the CLASS profile and/or website. When submitting written material, the following must be included:
- Explicit, written permission from the submitter to post the photograph on the CLASS profile and/or website.
- FetLife-compatible formating (if desired)
- FetLife usernames for:
- Any others with a creative interest in the writing
- For non-fiction accounts of CLASS events:
- All participants featured in the writing
- Event organiser
- Event host
If any of these individuals does not have a FetLife username, alternate contact information should be provided. Written permission (via email or PM) will be obtained by CLASS from each of these individuals prior to posting the writing. Additionally. Any of these individuals may request for the writing to be removed at any time. CLASS will attempt to honour all requests for removal as soon as possible, typically within 24 hours
All accepted writings will be uploaded as visible to all FetLifers and publicly posted to the website as applicable. CLASS will not transmit writings to a third party at any point in this process. However, those submitting and giving authorisation for the posting of writings are reminded that, once posted, CLASS is not able to guarantee that the writing will not be disseminated by third parties viewing the writing from the CLASS profile and/or website.
It is understood that conflicts will arise between CLASS members. Members of CLASS are encouraged to resolve issues among themselves, or to contact the appropriate authorities as necessary for serious issues.
However, members may also contact any member of the BOT if assistance is required. Information shared with a BOT member for this purpose may be shared with the rest of the BOT and other individuals involved in the issue during the conflict resolution process. The BOT will endeavour to resolve the matter to the satisfaction of all parties where feasible, but the primary goal of the BOT will be to support the continuing function and harmony of the CLASS group.
Note: This is a living document and will be updated periodically as described above. Latest update: 22 March 2017