# Pull Request Previews **URL:** \ **Category:** Need Help\ **Created:** [August 3, 2022, 12:43am UTC](https://community.doppler.com/t/pull-request-previews/708 "2022-08-03T00:43:28Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mattste](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/mattste/32/489_2.png) [@mattste](https://community.doppler.com/u/mattste)\ **Post date:** [August 3, 2022, 12:43am UTC](https://community.doppler.com/t/pull-request-previews/708/1 "2022-08-03T00:43:28Z")
I’m working on creating pull request previews support for my team. The goal is to create a config branch per pull request preview. This allows developers to customize secrets for just their own pull request preview. We have a service token that was generated and stored in our CI’s secrets store: ```auto doppler configs tokens create --access "read/write" --config pr_preview --project overwatch --name pr-preview-token --plain ``` We then try to create a config branch: ```auto doppler configs create --environment pr_preview --name pr_preview_test_v0 --project my-project --token pr-preview-token-value-here ``` This outputs the following error: ```auto Unable to create config Doppler Error: You do not have write access. ``` Is there a way to grant a service token the ability to create configs? ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [August 3, 2022, 12:53am UTC](https://community.doppler.com/t/pull-request-previews/708/2 "2022-08-03T00:53:16Z")
Hi @mattste and welcome to the Doppler community! Unfortunately not. Service tokens only allow secrets write access to a single config and cannot be used to modify the structure of a project. A personal token will allow you to do what you’re after but exercise great care as it grants the same level of access as the user account it belongs to. We are investigating more flexible permission models but for now, a personal token is your best bet for automating the creation of Doppler branch configs. ---
**Author:** ![mattste](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/mattste/32/489_2.png) [@mattste](https://community.doppler.com/u/mattste)\ **Post date:** [October 26, 2022, 10:46pm UTC](https://community.doppler.com/t/pull-request-previews/708/3 "2022-10-26T22:46:08Z")
Circling back here as I revisited this. It’d be ideal to have organization level scoped service tokens. Ideally, the following flow is supported: 1. Create an org level service token whose only permission is to create projects (ex. pull-request-1000-preview) and generate a service token for the created project 2. Use the generated service token to create configs for the project, set secrets and generate another service token that is read-only. ---
**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\ **Post date:** [November 7, 2022, 3:56pm UTC](https://community.doppler.com/t/pull-request-previews/708/4 "2022-11-07T15:56:16Z")
@mattste We’re actually working on a feature that will allow you to create custom tokens that have configurable permission sets. These will be workplace-level tokens, so it be almost exactly what you’re looking for here! ---
**Author:** ![jcprz](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/jcprz/32/853_2.png) [@jcprz](https://community.doppler.com/u/jcprz)\ **Post date:** [July 27, 2023, 3:21pm UTC](https://community.doppler.com/t/pull-request-previews/708/5 "2023-07-27T15:21:34Z")
I know my question doesn’t fall into the same category (access-related) than the original one, but I’m trying to integrate Doppler (DSO) on k8s and I templated the DopplerSecret manifests with helm for deploying my apps. The thing is that for a Pull Request Preview env I don’t see the ability of having branching configs set up there. I need to branch from say my root `develop` config and create this ephemeral environment based on this one (le’ts call it `develop_preview-pr-15`) and have this environment to interact with this ephemeral branched config which can be deleted easily as well using the CLI. Should I create a separate discussion for this? just let me know. Thank you! ---
**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\ **Post date:** [July 27, 2023, 3:33pm UTC](https://community.doppler.com/t/pull-request-previews/708/6 "2023-07-27T15:33:45Z")
@jcprz Probably this should be a separate post, but I can reply here. What you’re looking for will need some outside automation, but should be achievable using a [Service Account](https://docs.doppler.com/docs/service-accounts) with appropriate permissions set. It would need to have Admin permissions on the project to be able to create and delete branch configs. Outside of that, you’d need to generate and apply a `DopplerSecret` in k8s for your preview app to use. If you describe what you’re doing in more detail, I can see if I can give you any additional pointers.