<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Step Documentation</title>
    <link>https://step.dev/knowledgebase/30/categories/security/</link>
    <description>Recent content in Security on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 17 Oct 2022 14:25:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/30/categories/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Role management</title>
      <link>https://step.dev/knowledgebase/30/admindocs/role-management/</link>
      <pubDate>Mon, 17 Oct 2022 14:25:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/admindocs/role-management/</guid>
      <description>General concepts Every Step user is assigned a main role upon creation. With the default configuration of roles and rights, only users with the admin role can access Step projects without any further action.
Users with other roles need to be added as members of specific projects; for each project membership, a specific role is defined.
Role management is only available in the Enterprise Edition of Step. Pre-populated Roles Role Definition guest grants read-only access while preventing modifications or executions tester grants most privileges required to define and execute test plans developer in addition to tester rights, grants the ability to define keywords and administer individual projects admin grants all privileges Default access matrix By default, the following mapping of roles and rights is provided.</description>
    </item>
    
  </channel>
</rss>
