======Using an Encrypted PAT======

This note is only for //managers// of repositories inside //Git Winch//. 

The encrypted PAT that a manager receives from an owner can be used to create a repository or add/remove repository members. (Read about [[/gitlabapitoken1?do=export_xhtml|encrypted PAT here]])

Once the owner sends the encrypted PAT to the manager (Separately, not via Git Winch... say as an email, etc) the said manager makes sure that the //PAT API Token/Key// is left empty. i.e. nothing should be filled there. 

Instead, the manager can directly click any of buttons for creating a repository or adding a member or removing a member. //Git Winch// will notice that the //PAT API Token/key// is empty and will proceed to ask a series of questions to do the work.

When it asks for the Encrypted PAT; at that point, the manager should paste in the encrypted key that was obtained from the owner.

**Troubleshooting**\\

  - If the encrypted PAT is not working, it usually means that the owner of the PAT erroneously may have given the actual PAT (which should never be done, frankly) In this case, request the owner to create an encrypted version of the PAT as explained in this help.
  - Even with the correct encrypted PAT, it is possible that adding and removing members may not be possible. That is because //only managers// of a repository (and of course the owner) can do that work. So ask the owner, to make you the manager of the repository you want to add/remove members. 

----
[[concepts?do=export_xhtml|Read Concepts]] | [[topics?do=export_xhtml|Table of Contents]]