I have a website and I want to create two separate registered user groups. Ex. Student and Teacher. Both are registered user groups.
I found only documentation to separate registered users from guests.
Related
https://www.yammer.com/api/v1/users/ does not work and only gives me users in the current user’s Yammer network. I need every single user.
If All Company had an ID I could use https://www.yammer.com/api/v1/users/in_group/
Moreover, https://www.yammer.com/api/v1/groups does not seem to have All Company within it
On the backend, All Company is not actually a group. It behaves kind of like a group in the UI, but with notable difference like users not being able to leave All Company. This and other difference betray the fact that the Yammer backend does not in fact treat All Company as a normal group.
Hitting the users.json endpoint will give you data about all users in the users' current network. This list of users is the same as the list of users who are "members" of the All Company group for that network.
I am working on system that will manage orders. Orders can be created via admin or via customer. Employee can take orders and change it's status.
My system should have three global types of users:
Admin - this type of users mostly uses WEB interface. Admins have different access levels, so some of them can only create orders, and others - edit core info about pricing and so on.
Customer - this type of users uses customer's mobile app. Main action is to add and cancel orders.
Employee - this type of users uses employee's mobile app. Employees can see open orders, assign themselves to orders and change order statuses.
Also, Customer and Employee can be authorised with phone number, that can be changed at some time (independently of each other). Admins can be authorised with uname + pword.
Current solution has one table for Admins, one for Customers and one for Employees.
So first part of question is how to structure database properly?
The second part is about authorising in REST api. In current solution I have three endpoints, that are authireses usertype independently.
admins/auth
customers/auth
employees/auth
And my thoughts is to keep three tables as is, because each usertype is slightly different concept and really independent. And keep authorisation as is, but add something like roles and privileges to auth token to restrict access for some resources.
I have SugarCRM version 6.2 Community Edition with a custom module called Agents. Agents do not have User accounts. I want to allow Agents to log into the CRM instance. I understand to login we need User accounts.
But is it possible to allow Agents to log in without creating a User? How?
Or is possible to relate a User to an Agent so that when the User logs in he/she can view that Agent's details?
Why dont you just create a role for Agent and create users and assign to that Role . ( admin can create users and assign user to the Agent role)
At the end when you pull record from user table you can filter it based on role ( say agents) and use them in your custom module.
Anyway, For agents to login they will recieve auto-generated Email and password as and when admin creates them as Agents
I installed openfire on CentOs and it uses external database for authentification and user list.
I managed groups based on a user table and a friend listing so that each user is also a group that is is an administrator and populated with users that are (friends).
External users and authentication works fine.
The issue is that the buddy list is only populated when is check "enable contact list group sharing openfire" on group administration.
I want to make this option always enabled so that user can see each other in their buddy list.
this is an existing issue openfire issue
Are there any possible solutions or alternatives.
Edit:
In other words, I want to avoid adding the following three lines to the ofGroupProp table:
name sharedRoster.displayName groupname
name sharedRoster.groupList
name sharedRoster.showInRoster onlyGroup
In Google Apps, there is always a base/primary organization. But Google Apps can have subdomains and suborganizations both (or combination of those).
We want to be able to identify the currently logged-in user as being part of the overall organization, whether it be the primary org/domain or some subdomain or suborg. But when you get user info or license info, it returns the home domain of the currently logged in user as the ID for their organization. No ID is consistent across all subdomains or suborgs.
I've also tried listing all orgs using the organization apis, but that doesn't seem to work when trying to get the org info of the root org: https://developers.google.com/admin-sdk/directory/v1/guides/manage-org-units
Is there a way, given a particular Google Apps user, to determine what the primary organization is?
The only alternative we have is to treat every domain/subdomain in the Google Apps org as it's own independent org. This is less than ideal because now a Google Apps admin who manages all of their sub-orgs/subdomains in one place in Google will now have to manage a separate organization in our app for each domain in their overall org. This uses up extra resources in our system for creating these additional orgs, but more importantly creates a very confusing organization/user management model.
When you look at the Users resource for the two users, compare the customerId attribute. If they match, the two users are in the same Google Apps account. If they don't they're not.
Also, don't assume two logged in users are in the same Apps account. One could be an Apps account and one could be a consumer account even though they have the same SMTP domain.