This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| org [2025/07/08 18:35] – admin | org [2025/08/03 16:45] (current) – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======Organization | + | ======Organization code====== |
| - | This code is always needed for //Git Winch// to work. It represents the organization ...or the division in the organization. | + | This code is always needed for //Git Winch// to work fully. It represents the organization ...(or it can even be a division in an organization.) |
| - | If set correctly, | + | If this Org code was not found as the application started. Usually, that happens when running a fresh installation |
| - | We call this the //"orgname"// in these docs. | + | This //Org Code// is set using the text stored in a special file named //orgname.txt// in the same folder where the application was installed. |
| - | This //" | + | If set correctly, this code will be seen at the bottom left corner of the //Git Winch Client Application.// |
| - | **Owner can create the orgname.txt **\\ | + | In short, //Git Winch// |
| - | If you are the owner yourself, then you can create this //orgname// by attempting to create your first repository in the //Manage// page of //Git Winch.// Click the [+] button there and //Git Winch// will check if the // | + | |
| - | **Manager can also create the orgname.txt **\\ | + | So when you start the application, if it is found that the //orgname// is NOT available, |
| - | If you have been assigned as a manager of a repository by the owner, then you should | + | |
| - | //Once you; either as the owner or the manager, had created | + | //**NOTE:** The Org Code can only have alphanumeric characters and optionally, |
| - | //NOTE: //Orgname// can only have alphanumeric characters and optionally, you can also use underscores. A minimum of 4 characters | + | **What |
| + | As an owner, you can choose whatever name you want, as long as it is as per the specs given here... and someone else must not have claimed it. Once you get the Org code you must communicate this name to other team members. Best way to do that is simply share the file " | ||
| - | **What //orgname// to use?**\\ | + | **Changing this Org Code**\\ |
| - | As an owner, you can choose whatever name you want, as long as it is as per the specs given here. And you must communicate | + | Usually, you would use only ONE Org code and use that always. But in some offices, the same person may be working in different divisions. In that case, that person may want to change |
| - | **Changing this Org or Division | + | You can change the organization code when working inside the application: |
| - | Usually, you would use only ONE //orgname// code and use that always. But in some offices, | + | |
| - | You can change the organization code when working inside the application: Double click on the //orgname// at the bottm left corner, and it will prompt | + | {{ :setorgname.jpg? |
| + | |||
| + | //NOTE: If you want to create your own Org code, make sure you have sufficient credits balance. Some amount of credits would get deducted. Also, you would need to mark the checkbox. Do NOT give your own name if you do NOT plan to create a new code. If you are working for someone else, give the org code that they provided, along with the full name of the owner of that Org.// | ||
| **IMPORTANT**\\ | **IMPORTANT**\\ | ||
| - | If you work on a repository which is from a different// | + | If you work on a repository which is from a different |
| **Why?**\\ | **Why?**\\ | ||
| + | The //Org Code// is needed as a kind of ' | ||
| + | |||
| //Git Winch// is used by many organizations. Some of them may have multiple divisions in them. This is used to differentiate between them. Also, it reduces the chance of " | //Git Winch// is used by many organizations. Some of them may have multiple divisions in them. This is used to differentiate between them. Also, it reduces the chance of " | ||