All Collections
Clayton user licenses explained
Clayton user licenses explained
Lorenzo Frattini avatar
Written by Lorenzo Frattini
Updated over a week ago

License requirements

Clayton only reviews code from known developers. As long as who contributes to your code is a known developer in your team, Clayton will let you run code reviews on an unlimited number of projects.

We only require active contributors to be licensed and you can mark as inactive developers that are no longer active or graphic designers only contributing static resources.

This mechanism doesn't affect repo permission, we simply flag that contributor as no longer active in Clayton so they don't need to be licensed.

Using the web app

Some people like the way we integrate with version control systems so much, that wonder if their developers should access our web app in the first place.

There are a few advantages:

  • Onboard developers before they start coding. Clayton helps you onboarding developers, letting them know what the coding standards are, and when they change.

  • Override Clayton's findings. Sometimes, what is seen as a problem or a violation of your coding standards by Clayton, could be a conscious design decision, and should be deemed acceptable. Project leads can let Clayton know.

  • Metrics and dashboards. Clayton automatically collects and displays key metrics that help your team understand frequent problems, and target remediation initiatives.

  • Access suggested training resources. Clayton automatically suggests resources such as Trailhead modules, Salesforce Technical Resources and blog posts that are relevant to the issue detected.

  • Check blame. Clayton lets you see who introduced any problem, to help team members swarm on the issue and support each other. (Pro Tip: blaming people is not cool, please be supportive)

Did this answer your question?