Knowledge Base Article

About default Aurora community ranks

Aurora communities include a set of pre-defined, default ranks. Review these out-of-the-box ranks and their associated ranking formulas and decide which ones you want to include in your community rank structure.

The default ranks we’ve provided have the following names and ranking formulas:

Rank

Formula

Khoros

hasRole("Khoros")

Community Manager

hasRole("Administrator")

Moderator

hasRole("Moderator")

Honored Contributor

(registrationAge >= 300000) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (net_kudos_weight_received*4) >= 222500)

Esteemed Contributor

(registrationAge >= 250000) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 100000)

Respected Contributor

(registrationAge >= 200000) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 50000)

Trusted Contributor

(registrationAge >= 175000) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 30000)

Valued Contributor

(registrationAge >= 150000) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 20000)

Super Contributor

(registrationAge >= 120000) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 5000)

Regular Contributor

(registrationAge >= 86400) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 2000)

Frequent Contributor

(registrationAge >= 43200) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 750)

Contributor

(registrationAge >= 10080) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 200)

Occasional Contributor

(registrationAge >= 5670) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >= 50)

New Contributor

(registrationAge >= 2880) && ((net_threads) + (net_replies*2) + (net_blog_articles*10) + (net_blog_comments*1) + (net_idea_threads*5) + (net_idea_comments) + (net_published_tkb_articles*10) + (net_tkb_comments) + (net_accepted_solutions*15) + (net_kudos_weight_given*2) + (kudos_weight_received*4) >=1)

Senior Member

(registrationAge >= 43200) && (overall_posts==0) && ((message_views*.25)+(net_kudos_weight_given*2) >= 10000)

Established Member

(registrationAge >= 43200) && (overall_posts==0) && ((message_views*.25)+(net_kudos_weight_given*2) >= 5000)

Regular Visitor

(registrationAge >= 43200) && (overall_posts==0) && ((message_views*.25)+(net_kudos_weight_given*2) >= 2500)


For each of the provided ranks you intend to use, you should change the name to reflect the personality of your community. For example, if your brand is focused on music, you might want to reflect that theme in your ranks ("Beginner,""Rock Star,""Conductor"). Or, you might want to use more general rank names like"New Member,""Top Contributor,""Expert," or"Esteemed Contributor" that reflect a member’s status, contributions, and influence level in your community.

Rename, edit, or delete any of these ranks to meet your specific needs before launching your site. Additionally, you can create new ranks before or after you launch your site.

Related topics:

Updated 12 days ago
Version 8.0
  • Hi LauraV 

    Would you be able to reformat the table items so the items don't use smart quotes? They may cause issues when trying to copy/paste.

    For example,

    hasRole(“Administrator”)

    should be:

    hasRole("Administrator")

     

  • LauraV 
    What would be the difference between "net thread" and "gross thread" count? 
    When I think of income, gross is the amount before any deductions. 
    For a thread, how is that figure determined? 

  • LarryI's avatar
    LarryI
    Khoros Expert

    Stacey_Intel net_threads is the metric we use for:

    (Number of topics) - (Number of deleted topics) = net_threads

  • LauraV  In the current example formula table, the "Valued Contributor" registrationAge value is lower than the one for "Super Contributor", eventhough the required point value for the first rank is higher.

  • Does Aurora have the ability to have 2 separate rank ladders? For example, members with Role A utilize one rank ladder and members of Role B experience the other one. I know this can be done in Classic, just not sure about Aurora. Thank you.

    • Lief's avatar
      Lief
      Champion

      jennyweigle- I've come back to this a couple times and for I'm struggling with the use-case for a mirrored rank ladder?
      The documentation makes it look like it's simply duplicates of each of the ranks with a new/different criteria associated?
      The description for why just says "If you want a different icon for some people?"

      Best I can come up with, based on the example, is that maybe I want Employees to still be recognized within the ranking scheme but ALSO tagged with the corp icon? 
      I suppose I could "mirror" it again and put my MVPs out there.
      Employees of a certain dept could want that too.
      (could get kinda crazy)

      but then the documentation says (do NOT duplicate a rank if the criteria is ROLE BASED)...which makes me think I should stay away from this whole concept due to the complexity? Like what happens if i duplicate a rank and then sometime later I decide it's a good idea to make the Original rank role based for some reason?

      • LarryI's avatar
        LarryI
        Khoros Expert

        jennyweigle LauraV got you!

        Lief Great question! To start, this really deals with how you can leverage the feature today to create "variations" to a straightforward rank ladder.

        Some communities might want employees / partners to have a special icon // rank display and go through the same ranking structure as end users to maintain conformity. You could create rank ladder fragments associated with roles so users could in effect level up through "Superman" themed ranks or they could go through a "Batman" themed ranks.

        Food for thought: Since you can use roles and user entity custom fields in ranking requirements, you can make the ranking structure as complex as you want. The only real limitation (outside of supported metrics) to deal with is that the ordering of ranks matters as ranks requirements are assessed from the top to the bottom of the ladder when a user signs in.

        No matter how complex your structure is, if a user meets the requirements for a rank above in the ladder, they will achieve that rank. We won't hold your hand if you want to try to go crazy, but we do recommend that you test the logic of your rank ladder so you don't frustrate any users. 😉