<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Provider-Admin on Layer5 Documentation</title><link>/tags/provider-admin/</link><description>Recent content in Provider-Admin on Layer5 Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/provider-admin/index.xml" rel="self" type="application/rss+xml"/><item><title>Provider Initialization</title><link>/cloud/guides/self-hosted/deployment/provider-initialization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/cloud/guides/self-hosted/deployment/provider-initialization/</guid><description>&lt;p&gt;A new deployment has no users, so nobody can sign in to administer it. Provider initialization solves that: when the server starts with &lt;code&gt;INIT_CONFIG&lt;/code&gt; set, it creates the &lt;strong&gt;provider organization&lt;/strong&gt; and its first &lt;strong&gt;Provider Admin&lt;/strong&gt;. From that account, you create organizations, assign roles, and manage the deployment. See &lt;a href="/cloud/reference/default-permissions/"&gt;Roles and Permissions&lt;/a&gt; for what a Provider Admin can do.&lt;/p&gt;

&lt;h2 id="format" class="heading-link"&gt;
 Format
 &lt;a href="#format" class="heading-anchor" aria-label="Permalink to this heading"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;INIT_CONFIG&lt;/code&gt; holds a YAML document. In Helm, set it as a multiline string in &lt;code&gt;env.initConfig&lt;/code&gt;, or load it from a file with &lt;code&gt;--set-file env.initConfig=provider-init.yaml&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>