About this project
it-programming / web-development
Open
Create account: the pastor / user when entering the site will be able to create the account to manage his church.
(There is no need to do the hotsite, only the access programming. The website design is up to us)
Login: the pastor / user will login to access the system.
Recover password: the pastor can recover his password by receiving a link by email.
(There is no need to do the hotsite, only the access programming. The website design is up to us)
My Account (profile): the pastor / user logged in the system will be able to edit his own data.
Name, email, password, payment, etc.
Users: the main login (pastor / user) can create logins for other users to also access the system.
The main login will create access profiles. Limiting access according to the profile chosen for each user.
The user profile may or may not access the selected modules. And you can also choose which churches / branches the user will have access to.
Senior administrator user - does it all in all churches
Example: this user accesses the "People", "Heritage", "Events" screen, etc., Of all churches (headquarters and branches)
Branch administrator user - does everything only at the authorized church / branch.
Example 1: this user accesses people, heritage, events, etc., Only from his church / branch.
Example 2: He will create a user account for John to access only the "People" screen. John can only see the people at this church / branch.
Example 3: The Senior Administrator User can prohibit that user from accessing the "Financial" screen. Then, that user will be able to do everything in this church / branch, except access the "Financial" screen.
People
This is a register of people from the church. They can be "member" or "non-member".
Anyone can download the app and create an account.
After this registration (account / login in the app), this registration will appear on this screen. Here the pastor will approve as "member" or "non-member".
At the top of this page there will be a table or in the form of <tablet>, or <div>, or <ul>. You will have the registrations recently made by people on their own private phones through the app.
The pastor approves as "member" or "non-member", or excludes.
Once approved, the registration disappears from there and appears in the table below. This second table will contain all those registered.
Note: this screen will have a modal so that the pastor can also include someone who does not have a phone for example. Whoever does not have a phone, on this screen the administrator can register anyone.
Churches
When the pastor creates his account for the first time on the "create account" screen on the website. A field will be for the name of the church. And when he finishes, the pastor already enters the system with a registered church.
This church will be the main one by default. But, he will be able to create other churches (branches).
To use the system he will pay a fee.
Example 100.00 for the main church. For each church he adds he will have to pay an additional cost, for example 30.00 per church.
That is, if he creates the account and adds 2 more churches, he will pay 160.00 per month.
100.00 the main.
R $ 30.00 the filial church 1.
And R $ 30.00 for the branch church 2.
Dashboard
If the user is the Senior Administrator User, they will see the dashboard with data for all churches. Statistics and percentages of all.
Example: (if church / branch A had 5 new people registrations, and branch B had 3 new ones) that user will see "People: 8" (total).
If the branch administrator User , is from church / branch A, he will see only "People: 5".
If it is from church / branch B, he will see only "People: 3".
System HEAD
In the HEAD of the system you will have a combolist with the name of the churches / branches. For the Senior Administrator User, the default is the "all" option, so that he can see all the data for all churches together.
Example: if you have in this list selected "all".
When he goes to the "People" screen, he will be able to see all people from all churches / branches. If he later goes to the "Events" screen, he will only see events from that church / branch. If he changes in HEAD "all" to "church / branch A".
Wherever it goes in the system, it will only display data from "church / branch A".
If the pastor / user has more than one church, the dashboard will be with data from all churches.
Example: Total number of registered members, from all churches.
At the
In the upper right corner, you will have a combolist with the churches.
When the pastor logs in, he will open the main church. The dashboard is from the main church, the People screen will appear only people from the main church, etc.
At the top, if he clicks on the church list and changes to branch 1, the data is only displayed for church 1.
Category IT & Programming
Subcategory Web development
What is the scope of the project? Medium-sized change
Is this a project or a position? Project
I currently have I have specifications
Required availability As needed
API Integrations Social media (Facebook, Twitter, etc.), Payment Processor (Paypal, Stripe, etc.)
Roles needed Developer
Delivery term: Not specified
Skills needed