### How to manage a project / organization account #### Setup permissions Social DB allows to setup permissions for other accounts to post or edit all the content of given account. Currently there is no UI for that (component request): `near call social.near grant_write_permission '{"predecessor_id": "root.near", "keys": ["yourproject.near"]}' --accountId yourproject.near --deposit 0.000000000000000000000001` #### Posting via another account Under profile menu at the top, there is an option called "Pretend to be another account". Enter the `yourproject.near` name that you have permissions for. Your view will change as if you are that account. Now you can post under that account while still signing transactions as your main account. #### Giving full permissions Sometimes you will want to give full permissions to another user. There are two ways to do it: - Setup a multisig account - Add their full access key We will leave mutlisig account for another time (and we will have components for that). To add that user's full access key, ask them to pull their public key (one way for them to find it is by listing all keys via `near keys youraccount.near`). Make sure you have command line `near` yourself. To authorize your command line, you need to run `near login`. To add their key, run the next command: `near add-key yourproject.near <their public key>` There is no logout from command line, to properly do that you will need to delete the key that was added during the login: `near keys` to list all the keys, and `near delete-key <key>` the one that you have in `~/.near-credentials/yourproject.near.json`. PS. This does sound like having a component for this would be extremely helpful.