<p>It's likely that your &quot;site admin&quot; has embraced Craft's &quot;Project Config&quot; approach which allows for config changes to be stored in version-controllable files and has probably set <code>allowAdminChanges</code> to <code>false</code> in the <code>config/general.php</code> file. This is usually a good thing, but it sounds like you are accustomed to having access to those things. For background on the whys and hows of Project Config, see the docs: <a href="https://craftcms.com/docs/4.x/project-config.html" rel="nofollow noreferrer">https://craftcms.com/docs/4.x/project-config.html</a></p>
<p>It's best to wait until your admin gets back to you on this, but if they really are completely unreachable, if you can access that config/general.php file you should be able to delete that <code>allowAdminChanges</code> key, or set it to <code>true</code>. Beware that doing this may break any deployment workflows your developer might have set up. Ideally your site should have been built in a way that does not require you to have access to settings or plugins.</p>

CC BY-SA 4.0
2022-09-14T19:35:20.090Z
2022-09-14T19:35:20.090Z
James Smith
<p>They were there previously, and the site admin is not responding. Is there anything I'm able to do?<a href="https://i.sstatic.net/6Fblg.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/6Fblg.png" alt="enter image description here" /></a></p>

<settings>
Settings and Plugins 'missing'
# Settings and Plugins 'missing'

(Asked by: username_0 on 2022-09-14)

They were there previously, and the site admin is not responding. Is there anything I'm able to do?[![enter image description here](https://i.sstatic.net/6Fblg.png)](https://i.sstatic.net/6Fblg.png)

**Tags:** settings

---

## 1 answers

### Answer by username_1 on 2022-09-14. Score: 1

It's likely that your "site admin" has embraced Craft's "Project Config" approach which allows for config changes to be stored in version-controllable files and has probably set `allowAdminChanges` to `false` in the `config/general.php` file. This is usually a good thing, but it sounds like you are accustomed to having access to those things. For background on the whys and hows of Project Config, see the docs: <https://craftcms.com/docs/4.x/project-config.html>

It's best to wait until your admin gets back to you on this, but if they really are completely unreachable, if you can access that config/general.php file you should be able to delete that `allowAdminChanges` key, or set it to `true`. Beware that doing this may break any deployment workflows your developer might have set up. Ideally your site should have been built in a way that does not require you to have access to settings or plugins.


---

