Self Client, Zoho Projects, and User-level authentication

Hey everyone,

I'm new to this style of development, and have some questions. I'm looking to develop a C# application that hooks into a company's Zoho Projects to read/write/do whatever. I have a Self Client setup, and the OAuth2 working just fine.

What I'm looking to achieve is require the users of the application to authenticate or login using their Zoho account against the company's project permissions. I may be poorly wording it, so for example.

- I launch the application, and generate the application's authentication token

- Before accessing the company's Zoho Projects information through the API, I need to login to the company's Zoho Projects page through the application, as if I'm logging in through the browser

- Upon success, the user's access level determines what calls they can do against the API in regards to reading and writing projects

Is there a way to achieve this? I don't want to have any anonymous user of the application to be able to make changes to the company's projects. Is this something that be done through Zoho's APIs, and I'm just missing the writeups, or is this something I have to roll out myself? Am I going about this the wrong way entirely?

If you can think of anything else an amateur like me would need to know about this, it would be greatly appreciated.

Thanks

Zoho Desk Resources

Desk Community Learning Series
Digest
Functions
Meetups
Kbase
Resources
Glossary
Desk Marketplace
MVP Corner
Word of the Day

Topic Participants
leec_30
Monica P

Sticky Posts
Building extensions #10: Fetch customized user inputs, store them globally at the app level, and access them across entities
This data storage concept enables you to store data related to your extension for both entity properties and extension properties. In our previous piece, we looked at how to store data for entities using entity properties. In this post, we'll look at
Building extensions #9: Store, retrieve, and access entity-specific data in widgets using data storage
Data storage - Overview Storing data related to the extension you are working on is essential. It can be saved as key-value pairs for an entity or extension, known as entity and extension properties, respectively. Data can be saved for the following entities
Building extensions #7: Create custom widgets for a simplified end-user experience
Discover the benefits of using widgets! We explored the significance of widgets, prerequisites, and the availability of JS SDK methods as part of our previous post. In this post, let's go over a detailed example of using widgets along with certain Zoho
Building extensions #6: Custom user interfaces with Widgets
Welcome to our post on Widgets for Zoho Projects! In our last post, we explored the significance of the connections feature, showed how to use it, and provided an example use case. In this article, we'll look at the importance of widgets, another feature
Building extensions #5: Integrating applications with Zoho Projects through Connections
In our last post, we discussed the essential features that a Zoho Projects extension can provide. Starting with this post andin every subsequent post going forward, we'll go through each of those features in depth, one by one, with an example use case.