Make Redmine Projects Public on Planio » History » Sprint/Milestone 19
Jan Schulz-Hofen, 03/17/2017 05:09 AM
1 | 1 | Jan Schulz-Hofen | # Make Redmine Projects Public on Planio |
---|---|---|---|
2 | |||
3 | 3 | Jan Schulz-Hofen | Planio is powered by Redmine and as such it offers the same great possibilities to **make Redmine projects public** on the Internet. You can choose whether your projects should be accessible to anyone – without the need to login, including search engines – or whether you'd like visitors to sign up first and leave their email address. You can also choose to manually confirm signups or confirm them automatically by sending an activation link in an email. |
4 | 1 | Jan Schulz-Hofen | |
5 | {{>toc}} |
||
6 | |||
7 | 16 | Jan Schulz-Hofen | ## What are Public Projects used for? |
8 | |||
9 | 19 | Jan Schulz-Hofen | Making your projects public is a great way to provide a **help desk for your customers**. Allow them to view FAQs or tutorial guides in the wiki ([like we do at Planio](https://support.plan.io/projects/planio-support-en)) or let them sign up to discuss in forums or create issues. |
10 | 17 | Jan Schulz-Hofen | |
11 | 19 | Jan Schulz-Hofen | Public projects in Planio are also great for collaboration on **Open Source projects**, for instance. You could also use it to host **public [Git or Subversion](https://plan.io/subversion-hosting-and-git-hosting/) Repositories**. |
12 | 13 | Jan Schulz-Hofen | |
13 | 1 | Jan Schulz-Hofen | Sounds fun? Follow this guide to learn how it's done. |
14 | |||
15 | ## What is a Public Project? |
||
16 | |||
17 | 4 | Jan Schulz-Hofen | A public project on on your Planio powered Redmine account is essentially that: **An open project that is available to the public**. |
18 | |||
19 | Normally, only the explicitly named members of a project in Planio can access it and outsiders cannot see what's going on. Let's change that! Here's how: |
||
20 | |||
21 | 1. Find your project or create a new one |
||
22 | 2. Navigating to **Settings** -\> **Information** in your project |
||
23 | 3. Check the box next to the **Public** label and click **Save** |
||
24 | |||
25 | 5 | Jan Schulz-Hofen | {{figure(Make Projects Public on Redmine by Planio) |
26 | !make_redmine_project_public@2x.png! |
||
27 | }} |
||
28 | |||
29 | 4 | Jan Schulz-Hofen | Congratulations! You now have a public project. |
30 | |||
31 | 6 | Jan Schulz-Hofen | ### Optional: Make all Projects Public by Default |
32 | 4 | Jan Schulz-Hofen | |
33 | Would you like to make all projects public by default? No problem: |
||
34 | |||
35 | 1. Navigate to *your avatar* -\> **Administration** -\> **Settings** -\> **Projects** |
||
36 | 2. Check **New projects are public by default** |
||
37 | 3. Click **Save** |
||
38 | |||
39 | Next, we'll learn how this change impacts your project and who will now be able to access it. |
||
40 | |||
41 | 1 | Jan Schulz-Hofen | ## The Anonymous & Non-Member Roles |
42 | |||
43 | 8 | Jan Schulz-Hofen | Now that you've made your project public, let's see how this changes the access permissions to it. |
44 | |||
45 | Please navigate to *your avatar* -\> **Administration** -\> **Roles and Permissions** for a moment. You'll see two special roles in addition to [your own individual roles](https://plan.io/roles-and-permissions/) which you can define yourself: |
||
46 | |||
47 | 1 | Jan Schulz-Hofen | {{figure(Non-Member and Anonymous Roles) |
48 | !non-member_and_anonymous_roles_in_redmine@2x.png! |
||
49 | }} |
||
50 | 10 | Jan Schulz-Hofen | |
51 | ### The **Non-Member** Role |
||
52 | |||
53 | Click on the **Non-Member** role to pull up its permissions. What you configure here will govern what **any user in your Planio account** will be allowed to see and do in your **public projects**. |
||
54 | |||
55 | 12 | Jan Schulz-Hofen | Specifically, this means that you won't have to add users to this public project anymore to give them access to it. Any user who does not have a specific role in the project automatically gets the permissions set in the **Non-Member** role. Users who *are members* in a public project will have all permissions from both the **Non-Member** role and their explicit membership roles combined. |
56 | 10 | Jan Schulz-Hofen | |
57 | 11 | Jan Schulz-Hofen | {{figure(Permissions of the Non-Member role) |
58 | !permissions_of_non-member_role@2x.png! |
||
59 | }} |
||
60 | |||
61 | 10 | Jan Schulz-Hofen | ### The **Anonymous** Role |
62 | 9 | Jan Schulz-Hofen | |
63 | 1 | Jan Schulz-Hofen | ### Individually Adding Anonymous and Non-Members to Projects |
64 | 7 | Jan Schulz-Hofen | |
65 | ## Do Not Require Authentication |
||
66 | 1 | Jan Schulz-Hofen | |
67 | ## User registration |
||
68 | |||
69 | ### Activation options |
||
70 | |||
71 | ### Conversion Optimization |