Gatekeeper Guide

Index

  1. Introduction
  2. The Role of a Gatekeeper
    1. Current Initiate Forums
    2. Application Mods
  3. Initiate Applications
    1. Application Form
    2. Moderator Actions
    3. AdminCP
    4. 0 Point Warning
    5. Recruitment Lock Down
  4. Full Membership Applications
    1. Application Form
    2. Detailed Mentor Referral
    3. Moderator Actions
    4. Voting
    5. AdminCP
    6. 0 Point Warning
    7. Assigning TS Ranks
  5. End of Cohort
    1. Cohort Report
    2. Full Membership Application Update
    3. Update Initiate Acceptance Mods
  6. Chain of Command

Introduction

Firstly, we’d like to thank you for your help! The role of officer is voluntary. It comes with the prestige of a higher ranking than members but also comes with a lot more work. If you are reading this you have been selected for a Gatekeeper position in the DI HQ.

This guide will provide you with the information you need to become a Gatekeeper and should always be referred to for assistance in your role as Gatekeeper in the future.  

The guide has been divided into chapters, and structured to help provide easy access to the various aspects of your role. All chapters are hyperlinked in the index on the previous page to make navigation easier.

You should consider any information you are given in HQ discussions on TS or PMs on Forums to be private and it should only be discussed with other HQ officers. Also any information given to you in confidence by users regarding applications should also be treated private and only discussed with HQ officers that require the information.

Back to Index

 

The Role of a Gatekeeper

As Gatekeeper you are responsible for handling applications. These applications include Initiate applications from new users looking to join the clan and the monthly Full Membership applications from Initiates applying to become Full Members of DI.

Any queries or questions regarding either application type would be directed to Gatekeepers and you would be responsible for answering these.

As well as your Gatekeeper responsibilities all HQ officers will occasionally be asked to attend meetings or give their feedback on various HQ topics.

As Gatekeeper there are two vital sections of the forums you need to watch closely, it is recommended that you follow both of these. These sections are:

Initiate Applications: http://forum.dmg-inc.com/forum/7-initiate-applications/

Full Membership Applications: http://forum.dmg-inc.com/forum/28-full-member-applications/

Initiate application section should be checked as often as possible. The full member application section is only open for posting from X to Y each month (Dates specified in the Cohort topic in Ludus Magnum for that month). When this is open it also needs to be checked as often as possible too.

Back to Index

 

Current Initiate Forums

As well as the above two mentioned forum sections, you also need to regularly check the current initiate forum to make sure it only contains applications from current initiates.. Any registered guests in there or anyone member (or higher) should be moved to the application graveyard.

These forums can be found here: http://forum.dmg-inc.com/forum/52-current-initiates/

There are two ways to move an application. The first is to open it and use moderator tools to select ‘Move’.

graveyard-1

The second is from within the forum topic where they are all listed. Here you will see a checkbox to the right of each application. Tick any you want to move.

graveyard-2

Once you select one (or more) applications you will get a new floating menu, always at the bottom of your screen. The arrow pointing to the right on this is the move option and will move any selected applications.

graveyard-3

Either of these methods will then give you a new popup screen.

graveyard-5

On this you need to select the correct Forum to move them to. This is Recruitment and Clan Management > Initiate Applications > Application Graveyard (See below image). Leave the link to new location box unticked, then click move.

graveyard-4

Back to Index

 

Application Mods

Application Mods are linked to the various moderator actions you can use on applications. The use of these is discussed in sections 3.2 and 4.4. For this section you just need to be aware of them.

application-mods-1

The first few are standard and would be used on most forums, Feature, Pin, Lock, Move and Merge. Theses aren’t any different on DI. The ones below these are custom designed for DI, they differ depending where you are on the forums. All of these are controlled in the AdminCP (Admin Control Panel). To login in to the AdminCP go to the top of the forum page and click your name. From the drop down menu select AdminCP.

admincp-1

This will open a login screen. Use the same login details you use for the forums to login. After logging in click ‘Community’ on the left hand side. This will give you a list of all Application Mods used across the DI forums. To the right of each Application Mod you will see tools that can be used.

application-mods-2

Enabled (or Disabled) tell you if that Mod is in use or not. Disabled Mods will not show up as an option on the forums. Next, you have the edit button. This will allow you to make changes to Mods and will be the button you use most. Then you have the copy button. Rarely used. Finally, the delete button. Never use unless you are 100% sure you should be deleting a Mod.

I will focus on the edit button, as you will have little use of the others. Clicking this will open up the Mod you clicked it for, giving you access to the options for the Mod and the ability to edit the content.

First section you see is Settings. This contains three options. The name of the Mod, the Forum section the Mod is available in and a tick box to make the Mod available on all of the Forums. Very rare you would change any of these.

application-mods-3

The next section you see is Properties. These are actions that happen to the Forum topic when the Mod is used. You can Lock or Unlock, Pin or Unpin, Hide or Unhide a topic automatically with a Mod from these settings. You can also move a topic to a different part of the forums, select where to move it to and leave a link to the new location. Again you will very rarely use this section.

application-mods-4

The second last section is Title. Here you can add text to the start or end of an application automatically by selecting a Mod. For example the below Mod would add [Awaiting Reply] to an application you have asked a question on, so the applicant is aware you are waiting for a reply from them. Again it is rare that you would need to change this.

application-mods-5

The final section is the most important for Gatekeepers and you may be changing it on a regular basis depending on how often division Commanders and Vices change. This section is where you decide to add an automatic reply or not. Most Gatekeeper Mods will have a reply.

application-mods-6

If you select to add a reply you can then put the message you’d like to appear with the Mod in the box below. Gatekeepers are responsible for keeping their Mods up to date and ensuring the information within them is correct. This means making sure all links and/or any users within the replies are correct.

I will use the Mod for accepting a new initiate into division three as an example. Below is an extract from that message.

application-mods-7

Here you can see there is a link to the Code of Ops. This link must be correct and working. There are also links to the division Commander and the division Vice. These links must be updated everytime there is a change in division Command. You must regularly check the Master Division Registry (MDR) to make sure they are up to date and if they aren’t update them.

MDR: http://forum.dmg-inc.com/topic/19324-~-master-division-registry-~/

Back to Index

 

Initiate Applications

Initiates are vital to the growth of DI, without new blood we will stagnate as a clan and then slowly start to decline as current members leave. DI is a very good clan though so we do not just allow anyone to join. Anyone looking to join must complete an application form. Once the form is completed to the Gatekeepers satisfaction that person will be made an Initiate and added to a Cohort.

When reviewing Initiate Applications you should ensure:

  • All questions are answered fully and correctly.
  • Any prerequisite requirements are met (Division specific).
  • Are Applicants applying for the first time or is this a reapplication.
  • Applicants do not have 3+ strikes.
  • Applicants are 15+ years old.
  • Is this their first, second or third application.

If the application needs to be corrected by the applicant, once it is corrected again check the above.

How to handle an application that isn’t the applicants first application:

  • All applicants are entitled to apply and join DI two times under the normal process.
  • Applicants are then allowed one final application.
  • The final (third) application must be approved by a gold star (Leadership) before it can be accepted.

If an applicant has previously been declined or removed from DI, they need to wait before applying again. The waiting periods depend on their previous rank, these are:

  • Registered guest – 3 days.
  • Initiate (or above) – 7 days.

There are two types of application that can be posted. They both use the same form but the answer to the first question will be different depending on the application type. These are Regular Entry Programme and Elite Entry Programme.

 

Regular Entry Program

Most applicants would undertake this program. Caters best for those who want to get the full experience of the clan throughout their Initiation period. An equal focus on community and game development forms the basis of the program which provides a very well rounded experience to initiates.

Who this is for:
Anyone with an interest in gaming and co-operative team play.

Requirements to become a Full Member:

  • Make at least 50 posts during your time in Initiation.
  • Attend at least 4+ Official Events and get the Event Attendance Tokens.
  • Be active on Forums daily, Inactivity of more than 3 days without a post in vacation will result in removal.
  • Pass “Voting” by the full members, with a “Yes” Vote of at least 90%.

 

Elite Entry Program

A specialist program for top tier players. Caters best for those who want to focus on utilising their very high end gaming skill-sets to Damage Inc through competitive play. A higher focus is placed on event attendance and game development than on community development. An applicant accepted through the elite entry programme receive the Initiate* rank. The * differentiates them from other Initiates.

Who this is for:

  • CSGO – Global Elites
  • Dota2 – 5K MMR or higher
  • League of Legends – Diamond IV or higher
  • Rocket League – Super Champion or higher

A Division can only have a number of Elite Initiates equal to 10% of their Division size. A 30 member Division can have 3 Elite Initiates, whereas a 50 member Division vcould have 5 Elite Initiates.

Requirements to become a Full Member:

  • Make at least 15 posts during your time in initiation.
  • Attend at least 8+ Official Events and get the Event Attendance Tokens.
  • Be active on Forums daily, Inactivity of more than 4 days without a post in vacation will result in removal.
  • Pass “Voting” by the full members, with a “Yes” Vote of at least 90%.

Back to Index

 

Application Form

1) Are you applying for the Regular or Elite Entry Program?:

This tells the Gatekeeper what entry program to review the application under.

2) What game are you applying for?:

This tells the Gatekeeper what division the user will be assigned to if accepted.

3) In-Game Information: (Name/Rank/Level/Experience, World/Server)

Help with assigning division where multiple are divisions are playing the same game. Also shows division Commander the level of experience then new recruit has.

4) Do you have a Steam Account? If so, post a link to your profile:

DI has various events that use Steam games, also officers use Steam as an alternative method of communication if unable to contact a user via TS or Forums.

a.) If you use Steam, have you added “-DI-” to your Steam name?(required):

To check if the requirement is met.

5) Idling in our Teamspeak is required whilst you are online. Will you be able to abide by this?:

This is a clan requirement and must be accepted before joining the clan. TS is our best and quickest form of communication. Quick communication can be a massive difference in most games.

6) Are you currently in any clans or teams? ~~DO NOT LEAVE BLANK~~ 

Will show us quickly if there are any issues with multi clanning that need to be addressed before they are allowed join DI.

a.) Name any previous clans/guilds/teams you were in: Leave blank if not applicable to you.

b.) How long were you there and why did you leave? Leave blank if not applicable to you.

This gives an insight into the user, a lot of clans could mean they are quick to quit. No clans will tell us this is a new experience for them.

7) Who invited you to join Damage Inc; where did you learn about us?

Tells us who in the clan is actively recruiting.

8) Do you acknowledge that you will be an Initiate for 4-7 weeks, and that you must achieve all requirements for full membership depending on the program you are entering?:

These requirements need to be completed before an Initiate can post a Full Membership application.

9) Why do you wish to join Damage Incorporated above other clans? (at least 2-3 lines of text required)

This can tell us what attracts users to DI and show us areas to focus on for recruitment. Also gives us the users initial impression of the clan.

10) Is this your first time applying for DI? ~~DO NOT LEAVE BLANK~~ 

a.) If No, when and why did you leave before? Leave blank if not applicable to you.

Need to check if they have waited the correct amount of time before reapplying.

b.) If you were removed from DI (or left) for any reason, why should we accept you back? (at least 2-3 lines of text required)  Leave blank if not applicable to you.

DI is a very good clan and if a user was removed we need a good reason to take them back. They need to have improved what resulted in their removal.

Note: At times you may come across a user that is having difficulty in understanding you, try not to ask the same question on their application more than twice. If they still don’t understand take it to PM. After that contact a ranking HQ officer for help, a member that speaks the same language may be required. You could also consider asking the person that recruited them to help.

Back to Index

 

Moderator Actions

Moderator Actions can be found in a drop down box at the bottom of the page when you have an Initiate application open. They look like this:

moderation-actions-1

  • [Initiate] Awaiting Reply:
    • Use this if anything is wrong with the application. Post your question/comment about the application then click this. It will change the topic title adding [Awaiting Reply] to the start and make a post in topic saying ‘Awaiting Reply from applicant. 36hours to respond.’
  • [Initiate] Accepted – DI-(appropriate division):
    • When you are happy with an application use this to accept the application. The division will depend on their primary game from question 1 of the application. You then need to update their profile (covered in section 3.3). This will post a message telling them the division they are assigned to and the next steps they need to take.
  • [Initiate] Move to Graveyard:
    • This will move the application to the Application Graveyard with no message posted. Used if an applicant posts they have decided not to join or if duplicate applications are posted.
  • Archive This Global:
    • Not used for applications.
  • [Initiate] Initiate Acknowledged:
    • Not used by Gatekeepers. This is for Commanders or Vices from a division to acknowledge the application after a Gatekeeper accepts it.
  • [Initiate] Declined:
    • Mainly used when an applicant doesn’t reply to you in the 36 hour deadline after you ask a question regarding their application. It moves the application to the Application Graveyard with the message ‘Declined: Failed to respond within 36 hours. You may reapply in 3 days.’ If the reason for declining is different edit the message. You then need to issue a 0 point warning to the applicant explaining why the application was declined. (covered in section 3.4).
  • Moderation History:
    • Shows you what, if any, moderation action have previously been done on the topic you are in and who did them.

Back to Index

 

AdminCP

After you accept an application you need to login to the Admin Control Panel (AdminCP) to update the user’s profile. Go to the top of the forum page and click your name. From the drop down menu select AdminCP.

admincp-1

This will open a login screen. Use the same login details you use for the forums to login. After logging in click ‘Members’ on the left hand side. On the right you will see a search bar, type the user’s name here to find them. Click the user’s name in the list below when it shows up.

Under the ‘Account Information’ tab you need to change ‘Group’ to Initiate. Then hit save.

profile-1

Next select the ‘Profile’ tab at the top. Here you need to change the ‘Cohort’ to the next available Cohort that hasn’t started and select the division you have assigned them to. Then save the page and close the AdminCP. You are now finished with this new Initiate.

profile-2

Back to Index

 

0 Point Warning

As users are unable to see their applications when they are moved to the Application Graveyard a 0 point warning was added to give them a message when they next login explaining why their application was declined.

To give the warning you hover over the user’s name in the the topic, click the cog wheel on the bottom right of the popup and select ‘warn user’

warn

A new popup will appear with 4 sections to fill out. Reason should be ‘Application Denied/Initiation’ Failed. Points should be 0. Note for member is where you explain to the member why the application was declined. Note for Moderators can just be ‘Declined Application’. Once filled out click ‘Issue Warning’ on bottom right.

warn-2

Back to Index

 

Recruitment Lock Down

Under certain circumstances a Division can decide to add an extra step to the Initiate application process. This step basically puts the Division under a recruitment lock down, meaning no new Initiates will be added to the Division without authorisation directly from the Commander. This could happen when dealing with treason issues, spy issues or at times of war. This step would need to be approved by clan leadership, normally through the Secretary-General or Director-General. Once it is in place, any applications that meet the criteria for acceptance would not be accepted by Gatekeepers. Instead the [Initiate] Pending Approval Mod would be used. This Mod only adds the following message to the topic:

Application complete and is now pending approval from Division Commander

This message should then be edited to mention the Division Commander in it using @CommanderName.

The Division Commander then decides if this applicant should be allowed into their Division. If they decide to accept them they use the [Initiate] Commander Approval Mod. This Mod only adds the following message to the topic:

I, as the Division Commander, have Approved the Acceptance of this application

From this point onward the application should be treat as a normal application and the [Initiate] Accepted – DI-(appropriate division) Mod should be used and users profile updated in the AdminCP.

Back to Index

 

Full Membership Applications

The Cohort for Initiates is one month long, so by the time Initiates are starting to post Full Membership Application they should be familiar with the clan and their division. This period tends to weed out any Initiates that wouldn’t have enough devotion or activity for a clan like DI, so you are mainly dealing with the the kinds of users we’d like in the clan now.

The requirements that must be met to become a Full Member are:

  • At least 4 Weeks as an Initiate
  • 50 Posts
  • Have read and understand the Code of Operations.
  • Had a good track record as an Initiate.
  • A Detailed Mentor Referral
  • Attend at least 4+ Official Events and get the Event Attendance Token
  • Pass “Voting” by the full members, with a “Yes” Vote of at least 90%

Back to Index

 

Application Form

1) How long have you been an Initiate? (Refer to your initiate app)

4 weeks as Initiate required before they can become a full member. Not 4 weeks before posting applications though.

2) Has your Primary Game, or Division changed during your initiation? If yes, why?

Changing very near the end of a Cohort can show they are not fitting in. Check to see if there were issues in last Division, it may just be a change of game with no issue at all.

3) Have you joined the Steam Group?

Not a requirement of joining but extra points are awarded towards final Cohort positions if done.

4) Have you been struck during your Initiation period? If so, why, and what have you done about it?

Can show if they had a good track record.

5) Have you completed the Final Test? If yes, what was your score?

Not a requirement of joining but extra points are awarded towards final Cohort positions if done.

6) Who is your mentor?

Required for the detailed mentor referral.

7) If you are declined due to too many “No” votes, will you reapply?

Tells us the level of dedication the Initiate has to DI.

Back to Index

 

Detailed Mentor Referral

Detailed mentor referral are required from an Initiates mentor. They are vital for an Initiate to progress to full membership as the mentor should know the Initiate very well so give us a good picture of what the are like and if they should be accepted into the clan. The detailed mentor referral uses this format:

1) How long have you known your Mentee?

This should be about one month, as they should have been assigned as mentor at the start of the cohort.

2) Why did your Mentee join Damage Inc and did they find what they were looking for?

Gives insight into the Initiate and gives us valuable impressions of the clan from an Initiate level.

3) Did your Mentee have issues with RSVPing and attending Clan Events during their cohort? If Yes give details and whether they improved.

Events are vital for building DI and maintaining the clan as a whole organisation instead of just a group of divisions. Initiates must understand this in order to progress as successful full members.

4) What do you consider to be the Mentee’s biggest area of development and/or contribution during your mentorship?

Lets the mentor tell us and the Initiate what areas the Initiate needs to work on improving.

5) Is your Mentee completely aware of the Code of Ops and did you discuss it with them in detail?

Reading and understanding the Code of Ops is a requirement for becoming a full member so this answer is vital.

6) Did your Mentee have issues being active on the Forums? If Yes give details and whether they improved.

Shows us if the Initiate has been active and where they could improve.

7) Was your Mentee striked during their initiation? If Yes give details and whether they learned and improved.

Will tell you if the Initiate had a good track record and if they are eligible for a top three position within the Cohort.

8) Was your Mentee responsive towards you as their Mentor on TeamSpeak  and to your forum PMs?

It is hard to be a good mentor if the Initiate fails to reply to you. This can show if the Initiate is ready to progress to full membership.

9) Would you Recommend this Initiate becoming a Full Member of Damage Inc? Answer carefully.

An Initiate requires a positive mentor report to become a full member this question is the basis of the recommendation.

10) Any other comments or observations you would like to include? 

The value of information here will depend on what is written. As it is an open question it gives the referral writer a chance to give you any information they feel would be valuable.

Back to Index

 

Moderator Actions

Moderator Actions can be found in a drop down box at the bottom of the page when you have an Initiate application open. They look like this:

moderation-actions-2

  • [Member] Awaiting Reply:
    • Use this if anything is wrong with the application. Post your question/comment about the application then click this. It will change the topic title adding [Awaiting Reply] to the start and make a post in topic saying ‘Application Marked as Awaiting Reply From Member’
  • [Member] Awaiting Referrals:
    • Once the application is completed correctly and fully, if the referrals haven’t yet all posted select this. It will change the topic title adding [Awaiting Referrals] to the start and make a post in topic saying ‘Application Approved, Marked as Awaiting Referrals’
  • [Member] Awaiting Voting:
    • When all referrals have posted and you are happy with them all select this. It will change the topic title adding [Awaiting Voting] to the start and make a post in topic saying ‘Application Approved, Marked as Awaiting Voting Period.’ Normally applications are left for a while for members to comment unless close to voting period.
  • [Member] Moving to Pending Voting:
    • Once the application is ready to be moved for voting select this. It will move the topic to Voting Pending section of the forums and make a post in topic saying ‘On Deck For Voting
  • Archive This Global:
    • Not used for applications.
  • 48 Hr Warning:
    • Any applications not moved to, or ready to be moved to pending voting should have this action taken 48 hours before voting is due to start. It will make a post in topic saying ‘This is your 48 hour warning! You must have all referrals and/or all answers correct in 48 hours or face movement to next month’s cohort.If you have any questions, feel free to contact me!’
  • [Member] Declined:
    • If an application is being declined because they failed to correct their application before voting opened or referrals were not posted in time use this action. It will change the topic title adding [D] to the start and make a post in topic saying ‘DECLINED : If this is your first time you will automatically be moved onto the next months cohort, if this is your second time you will be removed and can contact me as to why and when you can reapply.’ It will also move the topic to the Full Mbr Application Graveyard.
  • [Member] Voting Result 85% -89%:
    • If an application is being declined because they received 85% – 89% in voting use this action. It will change the topic title adding [D] to the start and make a post in topic saying ‘DECLINED: Your application has been declined as a result of receiving 85% – 89% in voting, which is below the required 90% to pass. Since you did achieve above 85% you will remain as an Initiate and be moved to the next cohort.’ It will also move the topic to the Full Mbr Application Graveyard.
  • [Member] Voting Result 84% or below:
    • If an application is being declined because they received 84% or below in voting use this action. It will change the topic title adding [D] to the start and make a post in topic saying ‘DECLINED: Your application has been declined as a result of receiving 84% or below in voting, which is below the required 90% to pass. Since you did not achieve above 85% you will be returned to Registered Guest and must wait 30 days before reapplying to DI. If you do reapply you must provide justification on why we should allow you return or state what has changed.’ It will also move the topic to the Full Mbr Application Graveyard.
  • Moderation History:
    • Shows you what, if any, moderation action have previously been done on the topic you are in and who did them.

Back to Index

 

Voting

Once the date specified for voting on the Cohort arrives all applications ready for voting need to be moved to Pending Voting using the Moderator Action ‘[Member] Moving to Pending Voting’ if they aren’t already moved.

Any applications in Pending Voting will have a new Moderator action, [Member] Send to Voting (48hrs).  This will move the topic to the Initiate Voting section of the forums and make a post in topic saying ‘Topic has been moved to Voting for 48 hours.

moderation-actions-3

All applications in Pending Voting need to have this action performed on them. You then need to edit each application and create a poll for each.

member-voting

The poll is to be public, private votes are not valid, and a simple yes or no question is sufficient. Question should be something like ‘Should this Initiate be made a full member’. Any no votes require a specific, explicit and honest post by the voter explaining their no vote.  Reasons must be well founded and represent a true and real risk to the integrity/reputation of the clan. (I.E.: abusive behaviour), Without such a post their vote is not valid.

Voting results:

  • 90%+ they pass and become a full member of DI.
  • 85% – 89% they will remain an initiate and automatically be placed into the next cohort for another chance.
  • 84% or below membership application declined and you will be demoted to Registered Guest.

If declined – they must wait 30 days until being able to re-apply to the clan (also requires justification on why we should allow this/what has changed etc)

Back to Index

 

AdminCP

If the voting is successful the applicant is to be promoted to “member” via the ACP. After you accept an application you need to login to the Admin Control Panel (AdminCP) to update the user’s profile. Go to the top of the forum page and click your name. From the drop down menu select AdminCP.

This will open a login screen. Use the same login details you use for the forums to login. After logging in click ‘Members’ on the left hand side. On the right you will see a search bar, type the user’s name here to find them. Click the user’s name in the list below when it shows up.

Under the ‘Account Information’ tab you need to change ‘Group’ to Member. Then hit save.

member-promotion

If an applicant receives 85% – 89% they will remain an initiate and automatically be placed into the next cohort for another chance. You should notify the Initiate Managers of any applicants moving onto the next cohort along with any Initiates that did not apply for full membership.

Any applicants that received 84% or below should be demoted to Registered Guest.

Back to Index

 

0 Point Warning

As users are unable to see their applications when they are moved to the Full Mbr Application Graveyard a 0 point warning was added to give them a message when they next login explaining why their application was declined.

To give the warning you hover over the user’s name in the the topic, click the cog wheel on the bottom right of the popup and select ‘warn user’

warn

A new popup will appear with 4 sections to fill out. Reason should be ‘Application Denied/Initiation Failed. Points’ should be 0. Note for member is where you explain to the member why the application was declined. Note for Moderators can just be ‘Declined Full Membership Application’. Once filled out click ‘Issue Warning’ on bottom right.

warn-2

Back to Index

 

Assigning TS Ranks

When a Cohort finished you need to change any initiates/initiates* that passed to full members and any that received 84% or below in voting to registered guests.

There are two ways to set them. The first, which can be used for anyone online is to right click on the person’s name in TS and select ‘Set Server Groups’. Click any additional groups they should be added to and/or click any groups they should be removed from. They belong to any groups that have a tick beside them.

ts-1

The second method is much better for changing large groups, but it is a bit more complex. At the top of TS go to Permissions, then Server Groups.

ts-2

This will open a popup screen. On the left hand side is a list of all server groups. On the right is a list of everyone in the group you have highlighted. You are interested in the Initiate and Member groups mainly.

ts-3

First you need to highlight the Initiate group. Using the search bar on the top right find the Initiate you are looking for. Before you remove them you need their unique ID so you can add them again. Right click their name and select ‘Copy Unique ID to clipboard’. It is safer to add them to the member group now.

ts-4

It is safer to add them to the member group now. Highlight the Member group on the left column. Click add on the bottom right. Paste their Unique ID in the popup and click ok. Now go back to the Initiate group, search them again. Highlight them and click remove on the bottom right.

ts-5

NOTE: If you are aware of anyone that has been promoted higher than member you can add them to the server group for their new rank instead of the member group.

Back to Index

 

End of Cohort

At the end of each Cohort (end of month) after the initiates have been handled there are a few tasks that are required to be done.

These are:

  1. Send Cohort report
  2. Check Full Membership Application Forum section for update
  3. Update initiate application Mods

They must be carried as quickly after the end of the Cohort as possible.

Back to Index

 

Cohort Report

A report should be then sent to the following positions within the clan, Leader, Chief of Staff, Deputy Chief of Staff, Activity Managers, Initiate Managers and other Gatekeepers. It should list all Initiates that had applications accepted, broken into their divisions and show if they moved to a rank higher th

You can also add statistics to the report showing, total number in Cohort, number who passed, number who did not pass but will be added to next Cohort, number who did not pass but will be made registered guests and a breakdown by division.

Below is a sample report based on a small fictional Cohort:

cohort-report

Back to Index

 

Full Membership Application Update

The Full Membership Application section of the forums has a message on it saying when it will next open (or close if it is currently open). This message needs to be updated each month. Gatekeepers do not update it but since they are the most frequent users in the applications section of the forums they should check it has been updated. If it hasn’t within a day or two from the end of a Cohort send a message to the current Deputy Chief of Staff, include all Gatekeepers in the message so multiple messages are not sent.

forum-close

Back to Index

 

Update Initiate Acceptance Mods

As was discussed in chapter 2.2, Gatekeepers are responsible for keeping their Mods up to date and ensuring the information within them is correct. The acceptance Mods for new clan applications automatically edits the title of the topic, adding the division and Cohort they are assigned to at the end of the title. After a Cohort ends all [Initiate] Accepted Mods need to be updated with the new Cohort month.

You need to login to the AdminCP. To login in to the AdminCP go to the top of the forum page and click your name. From the drop down menu select AdminCP. Anything with ‘[Initiate] Accepted’ in the title will need to be changed.

This will open a login screen. Use the same login details you use for the forums to login. After logging in click ‘Community’ on the left hand side. This will give you a list of all Application Mods used across the DI forums. To the right of each Application Mod you will see tools that can be used. You want to select the edit button, that looks like a pencil.

application-mods-8

Clicking this will open up the Mod you clicked it for, giving you access to the options for the Mod and the ability to edit the content. You want to scroll down to the ‘Title’ section. Here edit the second box, ‘Add to the end of the title’. Only change the month.

application-mods-9

Then scroll to the end of the page and click ‘Save’. Repeat for each [Initiate] Accepted Mod.

Back to Index

 

Chain of Command

As you can see above Gatekeepers are part of DI HQ. The chain of command for Gatekeepers is as follows:

  • Gatekeeper ranking directly above you.
  • Any Gatekeepers above them.
  • Head Administrator.
  • Chief of Staff.
  • Chief Aide-de-Camp
  • Leader.

Any higher ranking officer in the HQ may question your actions or give you instructions but these are who you report problems to. Make sure to respect the chain of command and go to the person directly above you first. You should only go higher up the chain on urgent issues when the person directly above you is unavailable.

You should add all officers between you and anyone higher up the chain of command to any communications with higher ranking officers. This way when your ranking officers log on next they know what has happened. You should also include any officers at the same level as you, where appropriate, to ensure they don’t start trying to deal with the issue as well.

Back to Index

Created by Xtream