Document autorization scenario for different roles for sending and and filling out scenario

## Description
"Er det mulig å gi noen tilgang til å fylle ut en tjeneste men ikke sende inn? Det ser ut som det kun er mulig å instansiere, skrive, lese og slette instanser ifølge"

## Screenshots
> Screenshots or links to Figma (make sure your sketch is public)

## Considerations
> Describe input (beyond tasks) on how the user story should be solved can be put here.

### Ops requirements
> Are there any requirements for monitoring? What is being built and what could go wrong?
> Are there any requirements related to backup?

## Acceptance criteria
> Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)

## Specification tasks

- [ ] Development tasks are defined

## Development tasks
> Add tasks here

## Test
> Add test cases here as checkboxes that are being tested as part of the changes.

## Definition of done
Verify that this issue meets [DoD](https://confluence.brreg.no/display/T3KP/Definition+of+Done#DefinitionofDone-DoD%E2%80%93utvikling) (Only for project members) before closing.

- [ ] Documentation is updated (if relevant)
- [ ] Technical documentation (docs.altinn.studio)
- [ ] User documentation (altinn.github.io/docs)
- [ ] QA
- [ ] Manual test is complete (if relevant)
- [ ] Automated test is implemented (if relevant)
- [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)

No files, tests, or entry points are identified. Start by clarifying the authorization roles for filling out versus sending a scenario, then document the supported permissions and their restrictions. Done means the scenario, allowed actions, and any negative cases are documented and the acceptance criteria are complete.

Written by the indexing model from the issue text.