As a sysadmin, you can control and change the number of points users receive automatically for different actions in the system - this can help influence the user's behavior.
Configuration for these settings is done in the Subsystem settings/feature setting based on what is the trigger for getting the points, as described in the below articles:
Why & How to configure workflow points -Acknowledge authors and co-authors for submission, and/or when their submission progress upon the workflow
Why & How to configure community feature points - Acknowledge users for being part of the innovation community., i.e. being collaborative and portioning the innovation process
Why & How to assign points to decision makers, task owners and stakeholder upon task completion -Acknowledge decision makers for participating in the process
Why & How to assign points to Idea Author(s) due to the feedback they get from the community
Acknowledge the authors/co-authors when their submission are being adopted/enriched by the community
Notes:
- Points that have already been previously acquired are not affected by changes made to the configuration. The changes will only affect future points gained. In addition, once an action is cancelled, points that were given directly on this action will be removed.
- By default, sysadmins do not get points.The logic behind it is we DO want sysadmins to be active, but not "compete" with the regular users on being acknowledged.
It's like being a parent and let your kids win :-)...
Other related articles
- How to manually assign user points
- Where are points displayed?
- Voting Points vs Passive Voting points
- Reasons for not receiving points