Organization portal walkthrough

Last Section:

The organization portal is pretty similar to the user portal. All announcements from an organization's repositories appear in the organization's profile. Private repository announcements will only be visible to members of the organization with read access to those repositories.

You can change the organization's profile photo, the display name of the organization, and the legal name of the organization by hovering the profile info in the upper left panel.


The repositories section in the upper right corner lists all of an organizations repositories. Organization members will see all the repositories they have read access to when visiting the organization's portal.

Members, invites & roles

The members option is where you can manager the members of your organization.

When you click the invite new member button in the lower left corner, you will be able to either search for a member by their name or username, or you can invite someone who does not have a floro account yet.

Finally you can also manage roles and modify the roles of an organizations members from the members & roles section.

Org settings

At this time Org Settings is a relatively brief tab with only the option to update your Organization's contact email. In future releases, this will like contain more administrative options relating to an organization.

Developer settings

Just as in the case of the user portal Developer Settings, Developer Settings in an organization is where API keys and Webhook Keys are managed.


Plugins and plugin management is covered in the developer documentation in the building plugins section.


As we have not implemented billing yet, there isn't much to say here for now. Floro will always be free for organizations with only public repositories, the same as GitHub. Once, an organization has one or more private repositories, we will charge that repository $25 per month per active organization member. There is an initial 5 member grace period before floro charges monthly. Failure to pay will result in a loss of push access and API access to all private repositories.

If you are self-hosting floro, billing does not apply to you.

Before you can push to a private repository owned by an organization, someone from the organization with billing access must acknowledge the future pricing of floro from the billing page.

Create repo

When you press the create repo from the organization portal, you will be able to create repositories owned by your organization.

Just as you have the option of creating a public or private repository from the user portal, you will have the same option when creating a repository owned by your organization.

Next section

We'll next be covering local repositories.