# 12-Nov-2026 — grant Atlas access when cloning a contributor schema [#272](https://github.com/Ramblers-GB/ngx-ramblers/issues/272)

## [build 1082](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/43395923344) — [commit c2e1026](https://github.com/Ramblers-GB/ngx-ramblers/commit/c2e1026c7384b671eefce170c32a963cfe8c0930)

_____

## What's new

- [Admin → Contributor Environment](https://ngx-ramblers.org.uk/admin/contributor-environment "{{siteUrl}}") clone creates a new schema whose name starts with the live database name, then copies collections into it.
- The platform grants the site's existing database user `readWrite` and `dbAdmin` on that schema. Atlas project credentials stay on the platform and are not deployed to group apps.
- The schema field shows an error if the name does not start with the live database name.
- A failed standard-assets copy names the first AWS error, not only the file list.